Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/921#discussion_r13395681
--- Diff:
yarn/stable/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -256,14 +256,22 @@ class ApplicationMaster(args:
ApplicationMasterArguments, conf: Configuration,
// TODO: Handle container failure
yarnAllocator.addResourceRequests(args.numExecutors)
// Exits the loop if the user thread exits.
- while (yarnAllocator.getNumExecutorsRunning < args.numExecutors &&
userThread.isAlive) {
+ val startTime = System.currentTimeMillis()
+ var usedTime = 0L
+ while ((yarnAllocator.getNumExecutorsRunning < args.numExecutors
+ && userThread.isAlive) && (usedTime < 1000L * 60 * 10)) {
--- End diff --
why do we need the usedTime check? Are you simply trying to get it to move
the launchReporterThread? If so I think I would prefer to see this done under
SPARK-1453 and have us fix more how the executors are launched and when we
start the user code.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
