hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3965) Add startup timestamp to nodemanager UI
Date Mon, 03 Aug 2015 15:54:05 GMT

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

Jason Lowe commented on YARN-3965:
----------------------------------

Test failure is unrelated and has recently been failing for other test-patch runs.  Filed
YARN-4010.

+1 lgtm.  Committing this.

> 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)

Mime
View raw message