hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period
Date Wed, 02 Dec 2015 14:26:10 GMT

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

Sunil G commented on YARN-4403:

Hi [~djp]
Thanks for the patch. Yes, its better to use {{MonotonicClock}} generally.
We also use SystemClock in proportional preemption policy, I feel as you mentioned a general
YARN ticket can handle all this together.

> (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period
> ------------------------------------------------------------------------------------
>                 Key: YARN-4403
>                 URL: https://issues.apache.org/jira/browse/YARN-4403
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Junping Du
>            Assignee: Junping Du
>            Priority: Critical
>         Attachments: YARN-4403.patch
> Currently, (AM/NM/Container)LivelinessMonitor use current system time to calculate a
duration of expire which could be broken by settimeofday. We should use Time.monotonicNow()

This message was sent by Atlassian JIRA

View raw message