[ https://issues.apache.org/jira/browse/SPARK-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062904#comment-14062904 ]
Henry Saputra commented on SPARK-2500: -------------------------------------- PR at https://github.com/apache/spark/pull/1424 > Move the loginfo for registering BlockManager to > BlockManagerMasterActor.register method > ---------------------------------------------------------------------------------------- > > Key: SPARK-2500 > URL: https://issues.apache.org/jira/browse/SPARK-2500 > Project: Spark > Issue Type: Improvement > Reporter: Henry Saputra > Assignee: Henry Saputra > Priority: Minor > > 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. -- This message was sent by Atlassian JIRA (v6.2#6252)