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

genericqa commented on YARN-6265:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  6s{color} 
| {color:red} YARN-6265 does not apply to trunk. Rebase required? Wrong Branch? 
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | YARN-6265 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12862234/YARN-6265.002.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-YARN-Build/21109/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> yarn.resourcemanager.fail-fast is used inconsistently
> -----------------------------------------------------
>
>                 Key: YARN-6265
>                 URL: https://issues.apache.org/jira/browse/YARN-6265
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.8.0
>            Reporter: Daniel Templeton
>            Assignee: Yuanbo Liu
>            Priority: Major
>         Attachments: YARN-6265.001.patch, YARN-6265.002.patch
>
>
> In capacity scheduler, the property is used to control whether an app with 
> no/bad queue should be killed.  In the state store, the property controls 
> whether a state store op failure should cause the RM to exit in non-HA mode.  
> Those are two very different things, and they should be separated.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to