InternalDistributedMember.toString() will use a host name if
SocketCreator.resolve_dns is set to true. Otherwise it uses a numeric
IP address.
resolve_dns is set to false if network partition detection is enabled in
order to avoid contacting a DNS server, which has been known to hang
when there are network problems and cause servers to not shut down.
So, if an IDM.toString() is built in a JVM that has resolve_dns set to
true it will not be equal to one from a JVM where it was set to false.
This may be what is affecting you.
Le 3/15/2016 8:45 AM, Jens Deppe a écrit :
Hi,
I'm finding that different components in Geode represent the member ID
differently. For example, some MBeans might show the member as
*10.118.33.250(server1:27254)<ec><v1>:1025* whereas the DistributionManager
might show the member as *deppe-mbp(server1:27254)<ec><v1>:1025*.
Unfortunately there are (many?) places where member equivalency is tested
by comparing the string representations. In this case, it fails.
Do we have any code that checks equivalency based on the string
representation of a member? I don't see anything in
InternalDistributedMember.
As an aside, there is some indication that this may only be relevant on Mac
OS and not on Linux variants.
Thanks
--Jens
