GitHub user JoshRosen opened a pull request:

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

    [SPARK-2977] Ensure ShuffleManager is created before ShuffleBlockManager

    This is intended to fix SPARK-2977.  Before, there was an implicit ordering 
dependency where we needed to know the ShuffleManager implementation before 
creating the ShuffleBlockManager.  This patch makes that dependency explicit by 
adding ShuffleManager to a bunch of constructors.
    
    I think it's a little odd for BlockManager to take a ShuffleManager only to 
pass it to ShuffleBlockManager without using it itself; there's an opportunity 
to clean this up later if we sever the circular dependencies between 
BlockManager and other components and pass those components to BlockManager's 
constructor.

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

    $ git pull https://github.com/JoshRosen/spark SPARK-2977

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

    https://github.com/apache/spark/pull/1976.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 #1976
    
----
commit a9cd1e1fcf2509ec683827436b4b2298ebdb5b67
Author: Josh Rosen <[email protected]>
Date:   2014-08-15T23:04:55Z

    [SPARK-2977] Ensure ShuffleManager is created before ShuffleBlockManager.
    
    This is intended to fix SPARK-2977.  Before, there was an implicit ordering
    dependency where we needed to know the ShuffleManager implementation before
    creating the ShuffleBlockManager.  This patch makes that dependency explicit
    by adding ShuffleManager to a bunch of constructors.
    
    I think it's a little odd for BlockManager to take a ShuffleManager only to
    pass it to ShuffleBlockManager without using it itself; there's an 
opportunity
    to clean this up later if we sever the circular dependencies between
    BlockManager and other components and pass those components to 
BlockManager's
    constructor.

----


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