[
https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528290#comment-15528290
]
Rohith Sharma K S commented on YARN-4205:
-----------------------------------------
After I revisited the patch with discussion points, below are 2 points to be
modified as a framework in current patch.
# The application-monitor-thread always register with ApplicationId. As a
framework to support multiple timeouts for same applications, it is require to
modify key as String rather than ApplicationId.
# ApplicationTimeouts has provided APIs to specify timeout. Instead API's, this
class can be modified to take multiple timeouts as Map<ApplicationTimeoutType,
long>. This allows user to provide multiple timeouts in flexible manner rather
than setting each specific API like setLifetime, setQueueTime, setRuntime.
> 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, 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: [email protected]
For additional commands, e-mail: [email protected]
