Build 2704: Discovery server keeps on returning a new set of publishers when auto load balancing is enabled
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| Trunk |
New
|
Undecided
|
Deepinder Setia | |||
Bug Description
System has 3 config and 4 control nodes, auto load balancing enabled for ifmap, below is the behaviour seen in discovery:
Discovery clients ( dns, control in this case) keep on switching from one instance of publisher to other instance(ifmap in this case)
check IN USE count of the instances of publisher
Discovery server keeps on returning a new set of publishers( even though system seemed to be load balanced 2,3,3 in this case) i.e. Discovery failed to figure out a stable allocation for ifmap
output1:
IfmapServer 10.204.216.17 nodea21:IfmapServer up up 2 0:00:03
IfmapServer 10.204.217.53 nodeg13:IfmapServer up up 3 0:00:01
IfmapServer 10.204.217.60 nodeg20:IfmapServer up up 3 0:00:04
output2:
IfmapServer 10.204.216.17 nodea21:IfmapServer up up 3 0:00:01
IfmapServer 10.204.217.53 nodeg13:IfmapServer up up 3 0:00:04
IfmapServer 10.204.217.60 nodeg20:IfmapServer up up 2 0:00:02
output3:
IfmapServer 10.204.216.17 nodea21:IfmapServer up up 3 0:00:05
IfmapServer 10.204.217.53 nodeg13:IfmapServer up up 2 0:00:03
IfmapServer 10.204.217.60 nodeg20:IfmapServer up up 3 0:00:01
discovery :
Service Type Remote IP Service Id Oper State Admin State In Use Time since last Heartbeat
OpServer 10.204.216.17 nodea21:OpServer up up 1 0:00:03
OpServer 10.204.217.53 nodeg13:OpServer up up 1 0:00:03
OpServer 10.204.217.60 nodeg20:OpServer up up 1 0:00:02
OpServer 10.204.217.107 nodeh3:OpServer up up 1 0:00:03
AlarmGenerator 10.204.216.17 nodea21:
AlarmGenerator 10.204.217.53 nodeg13:
AlarmGenerator 10.204.217.60 nodeg20:
AlarmGenerator 10.204.217.107 nodeh3:
IfmapServer 10.204.216.17 nodea21:IfmapServer up up 3 0:00:03
IfmapServer 10.204.217.53 nodeg13:IfmapServer up up 3 0:00:01
IfmapServer 10.204.217.60 nodeg20:IfmapServer up up 2 0:00:04
dns-server 10.204.216.17 nodea21:dns-server up up 4 0:00:04
dns-server 10.204.217.60 nodeg20:dns-server up up 0 8:32:12
dns-server 10.204.217.107 nodeh3:dns-server up up 4 0:00:00
xmpp-server 10.204.216.17 nodea21:xmpp-server up up 3 0:00:04
xmpp-server 10.204.217.60 nodeg20:xmpp-server up up 0 8:32:13
xmpp-server 10.204.217.107 nodeh3:xmpp-server up up 3 0:00:00
Collector 10.204.216.17 nodea21:Collector up up 20 0:00:05
Collector 10.204.217.53 nodeg13:Collector up up 21 0:00:02
Collector 10.204.217.60 nodeg20:Collector up up 24 0:00:01
Collector 10.204.217.107 nodeh3:Collector up up 21 0:00:04
ApiServer 10.204.216.17 nodea21:ApiServer up up 1 0:00:03
ApiServer 10.204.217.53 nodeg13:ApiServer up up 1 0:00:01
ApiServer 10.204.217.60 nodeg20:ApiServer up up 1 0:00:04
| Ankit Jain (ankitja) wrote | #1 |
