[
https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472732#comment-15472732
]
Vinod Kumar Vavilapalli commented on YARN-4205:
-----------------------------------------------
bq. And I believe monitoring interval should be configurable at RM level.
Okay, that makes sense. As long as we have a reasonable default that no-one
touches in practice (like the AM-liveliness configs), we are good.
Also yarn.app.lifetime.monitor.interval-sec ->
yarn.resourcemanager.app-timeouts-monitor.interval-sec ?
> 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
