[ https://jira.jboss.org/jira/browse/JGRP-860?page=com.atlassian.jira.plugi... ] Galder Zamarreno commented on JGRP-860: --------------------------------------- Bela, as talked to you in Brno, I had an idea of building a tool that would integrate the 3 tests that pretty much verify that nodes will be able to cluster together without any issues: - muticast test - view demo - larget state test Each of the test different scenarios that I've seen fail in customer's environment before. For example: sometimes multicasting does not work at all, sometimes multicast works but after stop/start, nodes do not join and other times large chunks cannot be transfered leading to farming issues that are rooted in network issues. My idea was not to have a central GUI of any sorts but potentially have some kind of coordinator (or 1st node where script is executed) and to start a "all-in-one" test in each node, indicated how many nodes would be in the cluster. Then, this test would first execute a multicast test where each individual node sends a message containing something different and each node verifies that it's received X number of messages. Once the coordinator figured out that all nodes had seen all messages from all, then you can move onto the next test, which is a combination of view demo and larget state test: - start with xml configuration and number of expected nodes in cluster (N) and state size to transfer (i.e 1 MB) - coordinator checks that view contains the number of expected nodes. - N-1 nodes that are only members must have received the state correctly (they know the size they should expect). - coordinator instructs 2nd node in cluster to die/shutdown and restart channel after T timeout. - coordinator checks that after instruction to shutdown, the view is updated correctly. - coordinator checks that after waiting long enough, the 2nd node is part of the view again and 2nd node received state correclty. - repeat this with N-1 nodes that are supposed to form the cluster. - once the current coordinator, c1, has done this with all nodes, it will shutdown its own channel so that a new coordinator is elected. - new coordinator, c2, will do the same thing all over again with the rest of nodes. - test ends when you'd done all permutations c1-cN. Some of Sacha's thoughts could be integrated with this, i.e. if all-in-one test fails with default configuration, try a TCP/MPING configuration...etc. Not sure whether adding benchmarking here is top priority here though. A tool that quickly and effectively show that something is wrong in the network is more important IMO. Maybe we can discuss this when you're in NE next week? As always, I'd love to do this but just gotta find out the time to do it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JGRP-860?page=com.atlassian.jira.plugi... ] Bela Ban updated JGRP-860: -------------------------- Fix Version/s: 3.x (was: 2.9) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira