You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2015/10/13 03:30:05 UTC
[jira] [Commented] (SPARK-10985) Avoid passing evicted blocks
throughout BlockManager / CacheManager
[ https://issues.apache.org/jira/browse/SPARK-10985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954202#comment-14954202 ]
Ted Yu commented on SPARK-10985:
--------------------------------
I am bit confused by the assignment of this JIRA.
Normally assignee is 'Apache Spark' before a pull request comes up.
It has been at least 2 days but I don't see PR.
Did I miss something ?
> Avoid passing evicted blocks throughout BlockManager / CacheManager
> -------------------------------------------------------------------
>
> Key: SPARK-10985
> URL: https://issues.apache.org/jira/browse/SPARK-10985
> Project: Spark
> Issue Type: Sub-task
> Components: Block Manager, Spark Core
> Reporter: Andrew Or
> Assignee: Bowen Zhang
> Priority: Minor
>
> 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