[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1842) Live node dropping out of cluster can cause duplicate message delivery

[ https://issues.jboss.org/browse/JBMESSAGING-1842?page=com.atlassian.jira.... ] Yong Hao Gao commented on JBMESSAGING-1842: ------------------------------------------- --- The Test Plan --- I - Verify the old failover works ( keepOldFailoverModel = true ) All existing tests should pass. All example works. JBM_CLUSTER table can be created, but no actions against it (timestamp updates and state changes). II - New failover model (keepOldFailoverModel = false) 0. verify All examples 1. Timestamp update • timestamp refresh interval: timestamp should be updated after each interval. 2. Normal Failover • Node shutdown, crash should cause failover to happen (if failoverOnNodeLeave is true) • Multiple nodes shutdown and crash 3. Node leaving cluster alive (Using JGroups util to simulate) • one node leaves the cluster: failover should not happen. the node serves as standalone server. the cluster quarantined it as expected. • if the node later shutdown/crash: failover should happen (if failoverOnNodeLeave is true) • if the node later re-joins the cluster: its quarantined state will be back to clustered. Repeat the above 3 steps with multiple node leaving, shutdown/crashing and rejoining. All message producers and consumers in the above test should work properly. The following should be checked: • if a cluster has some nodes (>1) in quarantined state, will a client side failover be limited to those normal nodes? or the client may failover to /from a quarantined node? What happens if the quarantined node rejoins the cluster? or what if it crashed/shutdown? • if client side failover works consistently in a dynamic situation where nodes consistently leave, rejoin, shutdown and crash? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira