You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Saisai Shao (JIRA)" <ji...@apache.org> on 2014/12/30 06:12:13 UTC
[jira] [Updated] (SPARK-4999) No need to put WAL-backed block into
block manager by default
[ https://issues.apache.org/jira/browse/SPARK-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saisai Shao updated SPARK-4999:
-------------------------------
Description: Currently WAL-backed block is read out from HDFS and put into BlockManger with storage level MEMORY_ONLY_SER by default, since WAL-backed block is already fault-tolerant, no need to put into BlockManger again by default. (was: Currently WAL-backed block is read out from HDFS and put into BlockManger with storage level MEMORY_ONLY by default, since WAL-backed block is already fault-tolerant, no need to put into BlockManger again by default.)
> No need to put WAL-backed block into block manager by default
> -------------------------------------------------------------
>
> Key: SPARK-4999
> URL: https://issues.apache.org/jira/browse/SPARK-4999
> Project: Spark
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 1.2.0
> Reporter: Saisai Shao
>
> Currently WAL-backed block is read out from HDFS and put into BlockManger with storage level MEMORY_ONLY_SER by default, since WAL-backed block is already fault-tolerant, no need to put into BlockManger again by default.
--
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