hadoop-yarn-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Junping Du updated YARN-4403:
-----------------------------
    Attachment: YARN-4403.patch

Update a patch to fix this issue in (AM/NM/Container)LivelinessMonitor. I think there are
also similar issues in other YARN components. Will file other JIRAs to follow up when we have
MonotonicClock there.

> (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()
instead.



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

Mime
View raw message