[QPID-6104] Test ReplicatedEnvironmentFacadeTest.testRemoveNodeFromGroup fails sporadically

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.31
• Component/s: Java Tests
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 16/Sep/14 11:18
• Updated: 25/Feb/15 21:14
• Resolved: 25/Feb/15 21:14

Description

Error Message

(JE 5.0.97) Could not determine master from helpers at:[localhost/127.0.0.1:10000]

Stacktrace

com.sleepycat.je.rep.UnknownMasterException: (JE 5.0.97) Could not determine master from helpers at:[localhost/127.0.0.1:10000]
	at com.sleepycat.je.rep.elections.Learner.findMaster(Learner.java:437)
	at com.sleepycat.je.rep.util.ReplicationGroupAdmin.getMasterSocket(ReplicationGroupAdmin.java:127)
	at com.sleepycat.je.rep.util.ReplicationGroupAdmin.doMessageExchange(ReplicationGroupAdmin.java:449)
	at com.sleepycat.je.rep.util.ReplicationGroupAdmin.getGroup(ReplicationGroupAdmin.java:262)
	at com.sleepycat.je.rep.util.ReplicationGroupAdmin.checkMember(ReplicationGroupAdmin.java:407)
	at com.sleepycat.je.rep.util.ReplicationGroupAdmin.removeMember(ReplicationGroupAdmin.java:244)
	at org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.removeNodeFromGroup(ReplicatedEnvironmentFacade.java:814)
	at org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacadeTest.testRemoveNodeFromGroup(ReplicatedEnvironmentFacadeTest.java:386)

DatabasePinger transaction was started when the second node environment was closed. Master was not assigned as designated primary.
As result, there was no majority and DatabasePinger transaction failed causing environment restart. Environment was not able to restart because there was no second node.

Setting "designated primary" on a Master node should resolve the test issue