[jira] [Comment Edited] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

["Karthik Kambatla (JIRA)" <ji...@apache.org>]

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

Karthik Kambatla edited comment on YARN-3980 at 11/22/15 9:11 PM:
------------------------------------------------------------------

Jenkins could be running on a (virtual) machine much slower than dev machines. Could we sleep for longer to ensure it doesn't fail on Jenkins. How about the following:
{code} 
for (int i = 0; i < 100; i++) {
  Thread.sleep(100);
  // check if heartbeat propagated
}
{code}


was (Author: kasha):
Jenkins could be running on a (virtual) machine much slower than dev machines. Could we sleep for longer to ensure it doesn't fail on Jenkins. How about the following:
{code} 
for (int i = 0; i < 100; i++) {
  Thread.sleep(100);
  // check if heartbeat propagated
}

> Plumb resource-utilization info in node heartbeat through to the scheduler
> --------------------------------------------------------------------------
>
>                 Key: YARN-3980
>                 URL: https://issues.apache.org/jira/browse/YARN-3980
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager, scheduler
>    Affects Versions: 2.7.1
>            Reporter: Karthik Kambatla
>            Assignee: Inigo Goiri
>         Attachments: YARN-3980-v0.patch, YARN-3980-v1.patch, YARN-3980-v2.patch, YARN-3980-v3.patch, YARN-3980-v4.patch, YARN-3980-v5.patch, YARN-3980-v6.patch, YARN-3980-v7.patch, YARN-3980-v8.patch
>
>
> YARN-1012 and YARN-3534 collect resource utilization information for all containers and the node respectively and send it to the RM on node heartbeat. We should plumb it through to the scheduler so the scheduler can make use of it. 



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