[
https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035910#comment-15035910
]
Junping Du commented on YARN-4403:
----------------------------------
Agree. LivelinessMonitor is more critical as it affects all YARN
daemons/containers lifecycle, so I prefer we get in this first.
Later, we can file two separate JIRAs: one for YARN and the other for MapReduce
to address other places. I am sure there are many places to change as all
timeout could be affected and we should be carefully. Hadoop/HDFS projects
should already adopt this early.
> (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)
