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

genericqa commented on YARN-8471:
---------------------------------

| (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  5s{color} 
| {color:red} YARN-8471 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-8471 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12929529/YARN-8471.001.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-YARN-Build/21138/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> YARN RM hangs and stops allocating resources when applications successively 
> running
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-8471
>                 URL: https://issues.apache.org/jira/browse/YARN-8471
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>            Reporter: tianjuan
>            Priority: Major
>             Fix For: 2.9.0
>
>         Attachments: YARN-8471.001.patch
>
>
> at some point RM just hangs and stops allocating resources. At the point RM 
> get hangs, YARN throw NullPointerException  at 
> RegularContainerAllocator#allocate, and 
> RegularContainerAllocator#preCheckForPlacementSet, and 
> RegularContainerAllocator#getLocalityWaitFactor



--
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