You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "nijel (JIRA)" <ji...@apache.org> on 2015/09/03 13:41:46 UTC
[jira] [Updated] (YARN-3813) Support Application timeout feature in
YARN.
[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nijel updated YARN-3813:
------------------------
Attachment: 0001-YARN-3813.patch
Sorry for the long delay..
Adding an initial patch.
The action on timeout is considered as KILL.
Please have a look. I will update the patch with more test cases after initial review.
Thanks
> 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)