GitHub user hsaputra opened a pull request:

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

    [SPARK-2500] Move the logInfo for registering BlockManager to 
BlockManagerMasterActor.register method

    PR for SPARK-2500
    
    Move the logInfo call for BlockManager to BlockManagerMasterActor.register 
instead of BlockManagerInfo constructor.
    
    Previously the loginfo call for registering the registering a BlockManager 
is happening in the BlockManagerInfo constructor. This kind of confusing 
because the code could call "new BlockManagerInfo" without actually registering 
a BlockManager and could confuse when reading the log files.

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

    $ git pull https://github.com/hsaputra/spark 
move_registerblockmanager_log_to_registration_method

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

    https://github.com/apache/spark/pull/1424.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 #1424
    
----
commit 3370b4a92a89c9952dc55c4686c704ad013155f8
Author: Henry Saputra <[email protected]>
Date:   2014-07-16T00:01:05Z

    Move the loginfo for BlockManager to BlockManagerMasterActor.register 
instead of BlockManagerInfo 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.
---

Reply via email to