GitHub user tgravescs reopened a pull request:

    https://github.com/apache/spark/pull/17748

    [SPARK-19812] YARN shuffle service fails to relocate recovery DB acro…

    …ss NFS directories
    
    ## What changes were proposed in this pull request?
    
    Change from using java Files.move to use Hadoop filesystem operations to 
move the directories.  The java Files.move does not work when moving 
directories across NFS mounts and in fact also says that if the directory has 
entries you should do a recursive move. We are already using Hadoop filesystem 
here so just use the local filesystem from there as it handles this properly.
    
    Note that the DB here is actually a directory of files and not just a 
single file, hence the change in the name of the local var.
    
    ## How was this patch tested?
    
    Ran YarnShuffleServiceSuite unit tests.  Unfortunately couldn't easily add 
one here since involves NFS.
    Ran manual tests to verify that the DB directories were properly moved 
across NFS mounted directories. Have been running this internally for weeks.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tgravescs/spark SPARK-19812

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/17748.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 #17748
    
----
commit e93f9848db0c09683ba59d2968c38ec7687302e2
Author: Tom Graves <[email protected]>
Date:   2017-04-24T16:24:41Z

    [SPARK-19812] YARN shuffle service fails to relocate recovery DB across NFS 
directories

----


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to