[
https://issues.apache.org/jira/browse/YARN-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648666#comment-14648666
]
Hong Zhiguo commented on YARN-3965:
-----------------------------------
Hi, [~jlowe], version 4 of the patch is uploaded with 2 changes:
1) NodeInfo.getNmStartupTime -> NodeInfo.getNMStartupTime
2) removed the "final" qualifier on NodeManager.nmStartupTime to avoid
checkstyle error:
{code}
Name 'nmStartupTime' must match pattern '^[A-Z][A-Z0-9]*(_[A-Z0-9]+)*$'
{code}
It's private with Getter. So it's OK not to be final.
> Add startup timestamp to nodemanager UI
> ---------------------------------------
>
> Key: YARN-3965
> URL: https://issues.apache.org/jira/browse/YARN-3965
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Reporter: Hong Zhiguo
> Assignee: Hong Zhiguo
> Priority: Minor
> Attachments: YARN-3965-2.patch, YARN-3965-3.patch, YARN-3965-4.patch,
> YARN-3965.patch
>
>
> We have startup timestamp for RM already, but don't for NM.
> Sometimes cluster operator modified configuration of all nodes and kicked off
> command to restart all NMs. He found out it's hard for him to check whether
> all NMs are restarted. Actually there's always some NMs didn't restart as he
> expected, which leads to some error later due to inconsistent configuration.
> If we have startup timestamp for NM, the operator could easily fetch it via
> NM webservice and find out which NM didn't restart, and take mannaul action
> for it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
