You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/09/16 18:14:33 UTC

[jira] [Resolved] (SPARK-1172) Improve naming of the BlockManager classes

     [ https://issues.apache.org/jira/browse/SPARK-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Wendell resolved SPARK-1172.
------------------------------------
    Resolution: Won't Fix

Okay let's close this until we do a braoder refactoring of the block manger.

> Improve naming of the BlockManager classes
> ------------------------------------------
>
>                 Key: SPARK-1172
>                 URL: https://issues.apache.org/jira/browse/SPARK-1172
>             Project: Spark
>          Issue Type: Improvement
>          Components: Block Manager
>            Reporter: Patrick Wendell
>            Assignee: Andrew Or
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> There is something called BlockManagerMaster that doesn't run on the driver (only on the Executors). There is a thing called BlockManagerWorker that is not really a "worker" component but a bridge between the connection manager and the block manager. I found these names confusing on my first read of this code and in the last week two other people have asked me to explain it to them. So perhaps we can find more intuitive names here... :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org