GitHub user YanTangZhai opened a pull request:
https://github.com/apache/spark/pull/1274
[SPARK-2324] SparkContext should not exit directly when spark.local.dir is
a list of multiple paths and one of them has error
The spark.local.dir is configured as a list of multiple paths as follows
/data1/sparkenv/local,/data2/sparkenv/local. If the disk data2 of the driver
node has error, the application will exit since DiskBlockManager exits directly
at createLocalDirs. If the disk data2 of the worker node has error, the
executor will exit either.
DiskBlockManager should not exit directly at createLocalDirs if one of
spark.local.dir has error. Since spark.local.dir has multiple paths, a problem
should not affect the overall situation.
I think DiskBlockManager could ignore the bad directory at createLocalDirs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/YanTangZhai/spark SPARK-2324
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/1274.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 #1274
----
commit df086731952c669e12673fd673d829b9fdd790a2
Author: yantangzhai <tyz0...@163.com>
Date: 2014-07-01T10:39:46Z
[SPARK-2324] SparkContext should not exit directly when spark.local.dir is
a list of multiple paths and one of them has error
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
