hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chun Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3094) reset timer for liveness monitors after RM recovery
Date Sat, 24 Jan 2015 02:34:36 GMT

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

Chun Chen commented on YARN-3094:
---------------------------------

Since RM can't receive ping from AM util ApplicationMasterService starts, I think it is more
accurate to reset time in AMLivelinessMonitor service after ApplicationMasterService starts.
I suggest init AMLivelinessMonitor service after ApplicationMasterService in RMActiveServices#serviceInit.

> reset timer for liveness monitors after RM recovery
> ---------------------------------------------------
>
>                 Key: YARN-3094
>                 URL: https://issues.apache.org/jira/browse/YARN-3094
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Jun Gong
>            Assignee: Jun Gong
>         Attachments: YARN-3094.patch
>
>
> When RM restarts, it will recover RMAppAttempts and registry them to AMLivenessMonitor
if they are not in final state. AM will time out in RM if the recover process takes long time
due to some reasons(e.g. too many apps). 
> In our system, we found the recover process took about 3 mins, and all AM time out.



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

Mime
View raw message