Mailing-List: contact dev-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
Date: Tue, 11 Apr 2017 21:29:41 +0000 (UTC)
From: "Hitesh Khamesra (JIRA)" <jira@apache.org>
To: dev@geode.apache.org
Message-ID: <JIRA.13026811.1481235821000.260135.1491946181705@Atlassian.JIRA>
In-Reply-To: <JIRA.13026811.1481235821000@Atlassian.JIRA>
References: <JIRA.13026811.1481235821000@Atlassian.JIRA> <JIRA.13026811.1481235821355@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (GEODE-2193) a member is kicked out immediately
 after joining
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 11 Apr 2017 21:29:45 -0000


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

Hitesh Khamesra reassigned GEODE-2193:
--------------------------------------

    Assignee: Hitesh Khamesra  (was: Bruce Schuchardt)

> a member is kicked out immediately after joining
> ------------------------------------------------
>
>                 Key: GEODE-2193
>                 URL: https://issues.apache.org/jira/browse/GEODE-2193
>             Project: Geode
>          Issue Type: Bug
>          Components: membership
>            Reporter: Bruce Schuchardt
>            Assignee: Hitesh Khamesra
>             Fix For: 1.1.0
>
>
> We have observed a number of cases where a member is kicked out immediately after joining.  The problem seems to be this:
> 1) the member sends a join request to the current coordinator
> 2) the current coordinator is in the process of shutting down
> 3) the current coordinator sends a view preparation message admitting the new member
> 4) another member receives the current coordinator's shutdown message and initiates becoming the coordinator
> 5) the new coordinator sends out a membership view that does not include the new member
> 6) the new member receives the prepared view and continues with startup
> 7) the new member sends startup messages to other members
> 8) the other members have the new coordinator's view and request removal of the new member as being rogue
> 9) the new coordinator sends a Leave message to the new member, causing it to issue a ForcedDisconnect
> The old coordinator should not initiate a new view if it is shutting down.  It needs to have cancellation & shutdown checks in its view transmission methods.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)