[
https://issues.jboss.org/browse/JGRP-1252?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1252:
--------------------------------
So, first of all, your view is *correct* (possibly after merging), even if it's duff,
isn't it ?
No, your config is correct. It's just the GossipRouter which maintains a table of
members and their associated information (e.g. IP address, logical name etc).
When GossipRouter is restarted, its table is empty until the existing members re-register.
If the existing members 1-3 don't re-register *before* the new client is started, then
you'll have a duff view, plus the cluster won't form correctly, until a merge
happens.
If the existing member re-register before the new client is started, then everything will
be fine.
You *could* reduce TCPGOSSIP.reconnect_interval (default is 10 secs), but then there's
a lot of activity going on when the GossipRouter is down.
In any case, if you *wait* for more than 10 second *after* restarting GR, but *before*
starting client 4, the existing members should have re-registered and GR should have a
fully populated table, so client 4 gets a correct view.
Note that you can trigger the fetching of this information by calling
probe.sh op=TCPGOSSIP.findInitialMembersAsString
Alternatively, everyone could do this programatically:
JChannel ch;
Discovery discovery_prot=(Discovery)ch.getProtocolStack().findProtocol(TCPGOSSIP.class);
discovery_prot.findInitialMembersAsString();
TCP Gossip Discovery Issue
--------------------------
Key: JGRP-1252
URL:
https://issues.jboss.org/browse/JGRP-1252
Project: JGroups
Issue Type: Bug
Affects Versions: 2.11
Environment: Windows XP and Solaris 5.10
Reporter: Grahame Rogers
Assignee: Vladimir Blagojevic
Labels: new_and_noteworthy
Fix For: 2.12
Attachments: JGroupsTest.zip, JGroupsTest.zip, JGroupsTest.zip, JGroupsTest.zip,
JGRP-1252-output.txt, JGRP-1252-output2.txt
I run the chat demo app that was shipped with an older version of Jgroups. Using tcp
transport, with tcpgossip for discovery I start up 2 instances of the chat application. I
then restart the gossip server and also another instance of the chat application. The 3rd
instance of the chat application receives a view update (membershipListener.viewAccepted)
only the logical name of one of the 2 previous instances of the chat client is incorrect.
I have detailed the results in:
http://old.nabble.com/TCPGossip-Discovery-Issue-td30227966.html
I will attach the test client to this bug report.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira