nijel commented on YARN-3813:

Thanks [~leftnoteasy] for the comments
I will update the patch with the code comments

bq. Do you plan to support updating lifetime when the application is running?
As per our understanding the following 2 are the use cases for this
1. User can increase the life time after some time and seeing the progress 
which already being monitored by timeout monitor
2. User can add a timeout for a running application so that this also will 

In both these cases the updated time out will be the total life time (from 
submitted time)

Please let us know you are thinking of any other scenario so that we can pla 
the interfaces accordingly.

bq. Do you plan to get lifetime via ApplicationReport, CLI, REST API?
Yes. As of now we plan for ApplicationReport. Based on the dynamic update the 
interfaces can be defined and handle as a subtask.

We had some offline chat as well. Few subtsks raised for the planned work. 
Please give your opinion

> 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, 0002_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

Reply via email to