[
https://issues.apache.org/jira/browse/YARN-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075133#comment-15075133
]
Sunil G commented on YARN-4526:
-------------------------------
Hi [~ka...@cloudera.com]
YARN-4403 introduced MonotonicClock and its available in util. So could we use
that instead of SystemClock itself in ControlledClock. MAPREDUCE-6562 was
trying to change MRApp to use MonotonicClock instead of SystemClock.
> 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
>
>
> 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)
