[
https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S updated YARN-4205:
------------------------------------
Attachment: 0007-YARN-4205.patch
Updated the patch with following major changes from previous one with more
general way.
# Moved RMAppLifetimeMonitor to separate package i.e
*org.apache.hadoop.yarn.server.resourcemanager.rmapp.monitor*
# Created RMAppToMonitor custom class to hold monitoring key. This consists of
ApplicationId+ApplicationTimeoutType. This is essential because same
application can have multiple timeouts.
# Removed ApplicationTimeouts class.
# In ApplicationSubmissionContext#setApplicationTimeouts is changed to
Map<ApplicationTimeoutType, Long>. In future, if we want to support more
timeouts like in Gour use case, we just need to add enum and provide
corresponding implementation in RMAppImpl.
> 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,
> 0003-YARN-4205.patch, 0004-YARN-4205.patch, 0005-YARN-4205.patch,
> 0006-YARN-4205.patch, 0007-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
