[mainline 3073]with multiple database nodes stopping of kafka service contrail-analytics-api going to initialization

mainline 3073 mitaka multinode

On Stopping kafka service in one of the database(database nodes :nodei17 nodei19 nodec28) ,
Contrail-analytics-api service status is going into initialization in all nodes.

Config Nodes : [u'nodei17', u'nodei19', u'nodec28']
Control Nodes : [u'nodei17', u'nodei19', u'nodec28']
Compute Nodes : [u'nodec10', u'nodei20']
Openstack Node : [u'nodeg37']
WebUI Node : [u'nodei17', u'nodei19', u'nodec28']
Analytics Nodes : [u'nodei17', u'nodei19', u'nodec28']
Database Nodes : [u'nodei17', u'nodei19', u'nodec28']
Physical Devices : [u'’]

root@nodei17:~# docker exec -it analyticsdb contrail-status
== Contrail Database ==
contrail-database: active

contrail-database-nodemgr active
kafka inactive

root@nodei17:~# docker exec -it analytics contrail-status
== Contrail Analytics ==
contrail-alarm-gen active
contrail-analytics-api initializing (UvePartitions:UVE-Aggregation[Partitions:20] connection down)

root@nodei19:~# docker exec -it analytics contrail-status
== Contrail Analytics ==
contrail-alarm-gen active
contrail-analytics-api initializing (UvePartitions:UVE-Aggregation[Partitions:20] connection down)

root@nodec28:~# docker exec -it analytics contrail-status
== Contrail Analytics ==
contrail-alarm-gen active
contrail-analytics-api initializing (UvePartitions:UVE-Aggregation[Partitions:20] connection down)
contrail-analytics-nodemgr active
contrail-collector initializing (KafkaPub:192.168.100.11:9092,192.168.100.14:9092,192.168.100.15:9092 connection down)