[
https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904688#comment-14904688
]
nijel commented on YARN-3813:
-----------------------------
thanks [~rohithsharma] and [~sunilg] for the comments
Updated patch with the the comment fix and test case for recovery.
bq. we are starting the monitor thread always regardless whether application
demands for applicationtimeout or not. I feel we can have a configuration to
enable this feature in RM level. Thoughts?
As i pinged you offline, this service will consider only apps which are
configured with a timeout. So leaving as a default service.
bq.RMAppTimeOutMonitor : When InterruptedException is thrown in the below code,
thread should break or throw back exception. So, thread will die else thread
wil be alive for ever
The while loop is guarded for interrupted state
> Support Application timeout feature in YARN.
> ---------------------------------------------
>
> Key: YARN-3813
> URL: https://issues.apache.org/jira/browse/YARN-3813
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: scheduler
> Reporter: nijel
> Assignee: nijel
> Attachments: 0001-YARN-3813.patch, YARN Application Timeout .pdf
>
>
> It will be useful to support Application Timeout in YARN. Some use cases are
> not worried about the output of the applications if the application is not
> completed in a specific time.
> *Background:*
> The requirement is to show the CDR statistics of last few minutes, say for
> every 5 minutes. The same Job will run continuously with different dataset.
> So one job will be started in every 5 minutes. The estimate time for this
> task is 2 minutes or lesser time.
> If the application is not completing in the given time the output is not
> useful.
> *Proposal*
> So idea is to support application timeout, with which timeout parameter is
> given while submitting the job.
> Here, user is expecting to finish (complete or kill) the application in the
> given time.
> One option for us is to move this logic to Application client (who submit the
> job).
> But it will be nice if it can be generic logic and can make more robust.
> Kindly provide your suggestions/opinion on this feature. If it sounds good, i
> will update the design doc and prototype patch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
