[jira] [Closed] (GEODE-3043) surprise member added when the member is already in the cluster

["Anthony Baker (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anthony Baker closed GEODE-3043.
--------------------------------

> surprise member added when the member is already in the cluster
> ---------------------------------------------------------------
>
>                 Key: GEODE-3043
>                 URL: https://issues.apache.org/jira/browse/GEODE-3043
>             Project: Geode
>          Issue Type: Bug
>          Components: membership
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>             Fix For: 1.2.0
>
>
> In a test that turns off use of TCP/IP stream sockets for cache communications (disable-tcp==true) it is possible for a member to be added as a "surprise member" even though it is already in the membership view.  This is due to our UDP messages not including the member's "name" in the sender ID included in the message and that InternalDistributedMember.compareTo() uses the member name in comparisons.  It doesn't really need to do that for partial IDs like these.
> {noformat}
> Admitting member <rs-CommunicationsBTTest-2017-05-24-05-11-31-client-10(gemfire_rs-CommunicationsBTTest-2017-05-24-05-11-31-client-10_25687:25687)<ec><v1>:1026>. Now there are 3 non-admin member(s).
> Admitting member <rs-CommunicationsBTTest-2017-05-24-05-11-31-client-10<ec><v1>:1026>. Now there are 4 non-admin member(s).
> .
> .
> .
> Membership: expiring membership of surprise member <rs-CommunicationsBTTest-2017-05-24-05-11-31-client-10<ec><v1>:1026>
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)