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

Hadoop QA commented on YARN-6020:
---------------------------------

| (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-6020 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-6020 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12844573/YARN-6020_1.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-YARN-Build/14453/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Resource.add exceed Int class`s length,when compute queue demand
> ----------------------------------------------------------------
>
>                 Key: YARN-6020
>                 URL: https://issues.apache.org/jira/browse/YARN-6020
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.4.0, 3.0.0-alpha1
>            Reporter: Feng Yuan
>            Assignee: Feng Yuan
>            Priority: Critical
>         Attachments: YARN-6020_1.patch
>
>
> Resource object use int to store memory field.When int exceed 
> Integer,MAX_VALUE,you will get a
> neagtive num of demand in FSQueue#updateDemand(),and your queue will nerver 
> get assign forever.
> I find this scenario still now in lasted code 3.0.x.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to