spark-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vanzin <>
Subject [GitHub] spark pull request: [SPARK-8167] Make tasks that fail from YARN pr...
Date Tue, 18 Aug 2015 21:29:52 GMT
Github user vanzin commented on a diff in the pull request:
    --- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
    @@ -207,6 +211,17 @@ private[yarn] class YarnAllocator(
    +   * Gets the executor loss reason for a disconnected executor.
    +   * Note that this method is expected to be called exactly once per executor ID.
    +   */
    +  def getExecutorLossReason(executorId: String): ExecutorLossReason = synchronized {
    +    allocateResources()
    +    // Expect to be asked for a loss reason once and exactly once.
    +    assert(completedExecutorExitReasons.contains(executorId))
    --- End diff --
    Isn't this racy? Is there a possibility that even after calling `allocateResources` we'll
still not know about why a particular executor has exited?

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 or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message