[
https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15463327#comment-15463327
]
Rohith Sharma K S commented on YARN-4205:
-----------------------------------------
bq. I agree with this above sentiment - we don't need another configuration
application.lifetimeout-monitor.interval-ms.
IIUC, the conversation between Sunil and Nijel had for starting another thread
i.e RMAppLifetimeMonitorThread. And I believe monitoring interval should be
configurable at RM level.
bq. The other important question is about when the clock start ticking for the
life-time. Clearly if we start it when the app gets submitted, we'd
automatically also handle YARN-2266
The new patch attached will be registering in NEW_SAVING transition. Basically
the time for storing RMStateStore also part of application life timeout.
RMstatStore storing should also part of app life time. Lifetime is considered
from NEW_SAVING to completing states i.e after RUNNING any states.
> Add a service for monitoring application life time out
> ------------------------------------------------------
>
> Key: YARN-4205
> URL: https://issues.apache.org/jira/browse/YARN-4205
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: scheduler
> Reporter: nijel
> Assignee: Rohith Sharma K S
> Attachments: 0001-YARN-4205.patch, 0002-YARN-4205.patch,
> YARN-4205_01.patch, YARN-4205_02.patch, YARN-4205_03.patch
>
>
> This JIRA intend to provide a lifetime monitor service.
> The service will monitor the applications where the life time is configured.
> If the application is running beyond the lifetime, it will be killed.
> The lifetime will be considered from the submit time.
> The thread monitoring interval is configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
