[
https://issues.apache.org/jira/browse/TWILL-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15806504#comment-15806504
]
ASF GitHub Bot commented on TWILL-187:
--------------------------------------
GitHub user chtyim opened a pull request:
https://github.com/apache/twill/pull/22
(TWILL-187) Added max start time
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chtyim/twill feature/twill-187
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/twill/pull/22.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #22
----
commit 5a2227303cfcf039d714f5b8917d06325066d17d
Author: Terence Yim <cht...@apache.org>
Date: 2017-01-07T01:56:53Z
(TWILL-187) Added max start time
----
> Max app start time should be configurable.
> ------------------------------------------
>
> Key: TWILL-187
> URL: https://issues.apache.org/jira/browse/TWILL-187
> Project: Apache Twill
> Issue Type: Improvement
> Reporter: Albert Shau
> Assignee: Terence Yim
> Fix For: 0.10.0
>
>
> The YarnTwillController waits at most 60 seconds
> (Constants.APPLICATION_MAX_START_SECONDS) for the app master to start up
> before killing the app. This number should be configurable instead of
> hardcoded. For example, it is a fairly common use case to schedule programs
> to run at regular intervals in a cluster. If a bunch of programs are started
> at the same time, this time out can be easily reached.
> On a small development cluster, I've reached this timeout if there are 30-40
> concurrent program starts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
