You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2016/01/13 00:01:39 UTC

[jira] [Commented] (YARN-4526) Make SystemClock singleton so AppSchedulingInfo could use it

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

Arun Suresh commented on YARN-4526:
-----------------------------------

[~kasha], The latest patch looks good. Can you probably kick jenkins once more ?
+1 pending that

> Make SystemClock singleton so AppSchedulingInfo could use it
> ------------------------------------------------------------
>
>                 Key: YARN-4526
>                 URL: https://issues.apache.org/jira/browse/YARN-4526
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: 2.8.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: yarn-4526-1.patch, yarn-4526-2.patch
>
>
> To track the time a request is received, we need to get current system time. For better testability of this, we are likely better off using a Clock instance that uses SystemClock by default. Instead of creating umpteen instances of SystemClock, we should just reuse the same instance. 



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