Le 11/21/2016 à 9:17 PM, Thacker, Dharam a écrit :
Hi,
Thanks Kirk & Bruce for the updates!
How would that be different in the restarted server ?
If server joins back on same host, same network interface and same
port, would that still be an issue ?
The "server port" is not part of the identity of a node in the cluster.
DistributedMember is the identity and it is based on the inet address
and the JGroups UDP port, which is selected from the
membership-port-range property.
Even after server changes its identity , how does that make difference
? As locator is still running even though in reconnect mode, new
member should be welcomed without any issue. Is that understanding
correct?
When a locator is in an auto-reconnect state its location services are
shut down in order to prevent new nodes from starting up in a
split-brain configuration. It only restarts its location services if it
is able to ping the UDP ports of enough members that were in its last
membership view to constitute a quorum.
My advice is to either set enable-network-partition-detection to false
or to use gfsh to shut down nodes. You could also use "kill -INT" since
Geode installs a shutdown hook that will cause it to perform an orderly
shutdown.
Thanks & Regards,
Dharam
Sent with Good Work (www.blackberry.com)
On Nov 22, 2016 01:31, Bruce Schuchardt <[email protected]> wrote:
I'm sorry but that's not correct. The auto-reconnect feature is
designed to reestablish quorum based on the old distributed identity of
the server, which is based on its IP address and UDP port. This will
most likely be completely different in the restarted server.
Le 11/21/2016 à 10:21 AM, Kirk Lund a écrit :
>
> PS: if you restart the server you killed, the reconnecting Locator
> should come back online. Disabling network partition detection as
> mentioned before will prevent this behavior.
>
This email is confidential and subject to important disclaimers and
conditions including on offers for the purchase or sale of securities,
accuracy and completeness of information, viruses, confidentiality,
legal privilege, and legal entity disclaimers, available at
http://www.jpmorgan.com/pages/disclosures/email
