[
https://issues.apache.org/jira/browse/YARN-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897281#comment-13897281
]
Hadoop QA commented on YARN-1641:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12628099/yarn-1641-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesApps
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3055//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3055//console
This message is automatically generated.
> ZK store should attempt a write periodically to ensure it is still Active
> -------------------------------------------------------------------------
>
> Key: YARN-1641
> URL: https://issues.apache.org/jira/browse/YARN-1641
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.3.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: yarn-1641-1.patch
>
>
> Fencing in ZK store kicks in when the RM tries to write something to the
> store. If the RM doesn't write anything to the store, it doesn't get fenced
> and can continue to assume being the Active.
> By periodically writing a file (say, every RM_ZK_TIMEOUT_MS seconds), we can
> ensure it gets fenced.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
