Gour Saha commented on YARN-4205:

Basically this point got discussed in earlier comments also, this JIRA is to 
track lifetime of an application. Defining lifetime is nothing but overall 
execution_time of application from submission time. Application get killed at 
any point of time. Basically user is imposing timeout for execution time. Use 
case is every 5 minutes he submits a application and user need output with in 5 
minutes. Use do not worry for time-consumed on statestore or allocation or any 
other which is not user facing also. 
Considering each stages of timeout, in future any other timeouts can be added 
to ApplicationTimeouts class. ApplicationTimeouts java doc also gives 
definition of lifetime.

So if the app is sitting in ACCEPTED state, as per current implementation the 
timeout monitor has started, right? If yes, then it does not fully satisfy the 
lifetime feature that YARN-4692 is looking for. In that case, we need to 
introduce monitor-start-time as a configurable parameter in 
ApplicationTimeouts. App submitters should be able to specify it along with the 
timeout value. The start time could be a set of relevant app state transition 
watermarks, like AppTimeoutsMonitorStartTime.SUBMISSION_TIME, 
AppTimeoutsMonitorStartTime.LAUNCH_TIME, etc. Thoughts?

> 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

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to