Mailing-List: contact reviews-help@spark.apache.org; run by ezmlm
Precedence: bulk
From: tgravescs <git@git.apache.org>
To: reviews@spark.apache.org
Reply-To: reviews@spark.apache.org
References: <git-pr-18905-spark@git.apache.org>
In-Reply-To: <git-pr-18905-spark@git.apache.org>
Subject: [GitHub] spark issue #18905: [SPARK-21660][YARN][Shuffle] Yarn ShuffleService failed ...
Content-Type: text/plain
Message-Id: <20170822142739.67D4DE0667@git1-us-west.apache.org>
Date: Tue, 22 Aug 2017 14:27:39 +0000 (UTC)
archived-at: Tue, 22 Aug 2017 14:27:41 -0000

Github user tgravescs commented on the issue:

    https://github.com/apache/spark/pull/18905
  
    The recovery path returned by yarn is supposed to be reliable and if it isn't working then the NM itself shouldn't run.  So in general you should just use that if you want spark to be able to recover.  If you don't have yarn recovery enabled them there is no need for us to write the DBs at all and I think we should change to not do that.
    
    I think this jira is a dup of https://issues.apache.org/jira/browse/SPARK-17321
    
    See my comments there.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org