[jira] [Resolved] (SPARK-10985) Avoid passing evicted blocks throughout BlockManager / CacheManager

["Andrew Or (JIRA)" <ji...@apache.org>]

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

Andrew Or resolved SPARK-10985.
-------------------------------
          Resolution: Fixed
            Assignee: Josh Rosen
       Fix Version/s: 2.0.0
    Target Version/s: 2.0.0

> Avoid passing evicted blocks throughout BlockManager / CacheManager
> -------------------------------------------------------------------
>
>                 Key: SPARK-10985
>                 URL: https://issues.apache.org/jira/browse/SPARK-10985
>             Project: Spark
>          Issue Type: Improvement
>          Components: Block Manager, Spark Core
>            Reporter: Andrew Or
>            Assignee: Josh Rosen
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> This is a minor refactoring task.
> Currently when we attempt to put a block in, we get back an array buffer of blocks that are dropped in the process. We do this to propagate these blocks back to our TaskContext, which will add them to its TaskMetrics so we can see them in the SparkUI storage tab properly.
> Now that we have TaskContext.get, we can just use that to propagate this information. This simplifies a lot of the signatures and gets rid of weird return types like the following everywhere:
> {code}
> ArrayBuffer[(BlockId, BlockStatus)]
> {code}



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