[ https://issues.jboss.org/browse/ISPN-1386?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1386: ----------------------------------- Description: The attached log is showing a test failure because a view is not stablished with the two remaining nodes: {code}2011-09-14 13:01:15,124 ERROR (testng-TopologyInfoBroadcastTest) [org.infinispan.test.fwk.UnitTestTestNGListener] Method testNodeLeaves(org.infinispan.distribution.topologyaware.TopologyInfoBroadcastTest) threw an exception java.lang.RuntimeException: Timed out before caches had complete views. Expected 2 members in each view. Views are as follows: [[TopologyInfoBroadcastTest-NodeA-20211(s0), TopologyInfoBroadcastTest-NodeB-32215(s1), TopologyInfoBroadcastTest-NodeC-36650(s2)], [TopologyInfoBroadcastTest-NodeA-20211(s0), TopologyInfoBroadcastTest-NodeB-32215(s1), TopologyInfoBroadcastTest-NodeC-36650(s2)]] {code} Having glanced some TRACE logs captured by Dan, it would appear that as NodeB is shutting down, TEST_PING finds it as a sole cluster member and finds another cluster formed of NodeA,NodeC, leading to a merge. This is somehow stopping a correct 2-node view being installed. Needs further investigation was: The attached log is showing a test failure because a view is not stablished with the two remaining nodes: {code}2011-09-14 13:01:15,124 ERROR (testng-TopologyInfoBroadcastTest) [org.infinispan.test.fwk.UnitTestTestNGListener] Method testNodeLeaves(org.infinispan.distribution.topologyaware.TopologyInfoBroadcastTest) threw an exception java.lang.RuntimeException: Timed out before caches had complete views. Expected 2 members in each view. Views are as follows: [[TopologyInfoBroadcastTest-NodeA-20211(s0), TopologyInfoBroadcastTest-NodeB-32215(s1), TopologyInfoBroadcastTest-NodeC-36650(s2)], [TopologyInfoBroadcastTest-NodeA-20211(s0), TopologyInfoBroadcastTest-NodeB-32215(s1), TopologyInfoBroadcastTest-NodeC-36650(s2)]] {code} Having glanced some TRACE logs captured by Dan, it would appear that as NodeB is shutting down, TEST_PING finds it as a sole cluster member and finds another cluster formed of NodeA,NodeC, leading to a merge. This is somehow stopping a correct 2-node view being installed. Needs further investigation -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1386?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-1386: ---------------------------------------- A very simple solution would be to leave MERGE out except in those tests that require MERGE. This shouldn't cause any issues in the testsuite because TEST_PING is deterministic in finding nodes and it's not really necessary to have MERGE as protection net for random situations in real life where nodes will only find each other after a MERGE. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1386?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-1386: ---------------------------------------- This is a good time to address ISPN-1229 cos otherwise we need to carry using regular expressions to filter things out of a stack which is ugly and could break very easily. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1386?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1386: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/533 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira