Hadoop QA commented on YARN-2721:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision b85919f.

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
                        Also please list what manual steps were performed to 
verify this patch.

    {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 

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5488//console

This message is automatically generated.

> Race condition: ZKRMStateStore retry logic may throw NodeExist exception 
> -------------------------------------------------------------------------
>                 Key: YARN-2721
>                 URL: https://issues.apache.org/jira/browse/YARN-2721
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Jian He
>            Assignee: Jian He
>             Fix For: 2.6.0
>         Attachments: YARN-2721.1.patch
> Blindly retrying operations in zookeeper will not work for non-idempotent 
> operations (like create znode). The reason is that the client can do a create 
> znode, but the response may not be returned because the server can die or 
> timeout. In case of retrying the create znode, it will throw a NODE_EXISTS 
> exception from the earlier create from the same session.  

This message was sent by Atlassian JIRA

Reply via email to