[
http://jira.jboss.com/jira/browse/JGRP-603?page=comments#action_12380083 ]
Bela Ban commented on JGRP-603:
-------------------------------
Actually, this works really well with "udp" (I probably tested "tcp"
when I thought I was testing "udp")...
But there are definitely issues with "tcp". Most issues are with
"tcp-nio", and we should look into those, although tcp-nio has not yet been
really well tested (and supported).
FLUSH: problems with TCP and concurrent startup/shutdowns
---------------------------------------------------------
Key: JGRP-603
URL:
http://jira.jboss.com/jira/browse/JGRP-603
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Vladimir Blagojevic
Priority: Critical
Fix For: 2.6
Attachments: jgtest.zip
The attached ZIP file has code that reproduces this.
Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and
"tcp-nio" if you want to test the different stacks.
To reproduce:
- Start a number of instances (e.g. 5) concurrently. This almost never works, even under
"udp". Joiners' JOIN requests time out and they have to retry (possibly
because the coord is busy with the FLUSH protocol). They become singleton members and
*never* merge !
- This works fine without FLUSH
- With "udp", it works almost always, with "tcp" it works 50% of the
time, with "tcp-nio" is almost never works
- Randomly kill and restart instances
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira