Description
Spark applications fail from time to time in yarn-cluster mode (but not in yarn-client mode) when yarn.nodemanager.local-dirs (Hadoop YARN config) is set to a comma-separated list of directories which are located on different disks/partitions.
Steps to reproduce:
1. Set yarn.nodemanager.local-dirs (in yarn-site.xml) to a list of directories located on different partitions (the more you set, the more likely it will be to reproduce the bug):
(...)
<property>
<name>yarn.nodemanager.local-dirs</name>
<value>file:/d1/yarn/local/nm-local-dir,file:/d2/yarn/local/nm-local-dir,file:/d3/yarn/local/nm-local-dir,file:/d4/yarn/local/nm-local-dir,file:/d5/yarn/local/nm-local-dir,file:/d6/yarn/local/nm-local-dir,file:/d7/yarn/local/nm-local-dir</value>
</property>
(...)
2. Launch (several times) an application in yarn-cluster mode, it will fail (apparently randomly) from time to time
Attachments
Attachments
Issue Links
- relates to
-
SPARK-4896 Don't redundantly copy executor dependencies in Utils.fetchFile
- Resolved
-
SPARK-4764 Ensure that files are fetched atomically
- Resolved
- links to