Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 13 Aug 2014 21:32:13 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12720181.1402341715472.76518.1407965533036@arcas>
In-Reply-To: <JIRA.12720181.1402341715472@arcas>
References: <JIRA.12720181.1402341715472@arcas>
Subject: [jira] [Commented] (YARN-2136) RMStateStore can explicitly handle
 store/update events when fenced
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096160#comment-14096160 ] 

Varun Saxena commented on YARN-2136:
------------------------------------

[~sunilg], on closer look at the code, when we close the RMStateStore, we close the ZKClients as well. Hence dispatcher queue draining shouldn't matter as ZKClient is already closed. 
Ofcourse as more than one thread is involved, AsyncDispatcher's event handling thread may pick up an event and process it(store/update operation) before RM can close RMStateStore(while switching to standby). 

But in my view, this shouldn't be too big an impact I think to warrant adding a FENCED state.


> RMStateStore can explicitly handle store/update events when fenced
> ------------------------------------------------------------------
>
>                 Key: YARN-2136
>                 URL: https://issues.apache.org/jira/browse/YARN-2136
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Jian He
>
> RMStateStore can choose to handle/ignore store/update events upfront instead of invoking more ZK operations if state store is at fenced state. 


--
This message was sent by Atlassian JIRA
(v6.2#6252)