hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5692) Support more application timeout types
Date Thu, 29 Sep 2016 15:16:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533049#comment-15533049

Rohith Sharma K S commented on YARN-5692:

Re posting [~gsaha]'s comment from YARN-4205
YARN-4692 also needs total execution timeout of application. It does not need queue or state-store
timeouts. The only additional thing it needs, is the monitor start time to provide options
YARN-4692 is for long running or semi long-running services. Long running services are meant
to run forever. Semi long-running services are meant to run for several hours or few days
or weeks. For the semi long-running usecases, we have applications like a CI (continuous-integration)
app or a System Test app, which typically needs several hours to finish its job. CI app or
System Test app owners are not going to be happy that their app did not run at all, even though
it was given a timeout of 10 hours because YARN got a chance to allocate resource to it at
the 9:59 hour mark since submission. That is why we need LAUNCH_FIRST.
LAUNCH_EVERYTIME will cover scenarios like say a load test app needs to run end-to-end for
at least 2 days straight to certify a product. If such an app is pre-empted at say the 47
hour mark, it needs a fresh 48 hour lifetime the next time it is re-launched.

> Support more application timeout types
> --------------------------------------
>                 Key: YARN-5692
>                 URL: https://issues.apache.org/jira/browse/YARN-5692
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
> YARN-4205 adds up general framework to monitor application for its timeout. And it support
for monitoring application for its lifetime i.e monitoring start from submitted_time. 
> Some users might need to monitor application for different phases. Say, some users wants
monitor from launched, some are required after registration and so on. Specific use cases
are mentioned in [comment|https://issues.apache.org/jira/browse/YARN-4205?focusedCommentId=15525225&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15525225]
by [~gsaha] which need to address as part of this JIRA.
> This JIRA is open for discussing more use cases and try to solve those.

This message was sent by Atlassian JIRA

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

View raw message