[
https://issues.apache.org/jira/browse/TWILL-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15806512#comment-15806512
]
ASF GitHub Bot commented on TWILL-187:
--------------------------------------
Github user gokulavasan commented on a diff in the pull request:
https://github.com/apache/twill/pull/22#discussion_r95049555
--- Diff: twill-api/src/main/java/org/apache/twill/api/TwillPreparer.java
---
@@ -257,8 +258,19 @@
TwillPreparer setLogLevels(String runnableName, Map<String,
LogEntry.Level> logLevelsForRunnable);
/**
- * Starts the application.
+ * Starts the application. It's the same as calling {@link #start(long,
TimeUnit)} with timeout of 60 seconds.
--- End diff --
Is there any constant that we can refer to for '60' ?
> 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)
