[
https://issues.apache.org/jira/browse/SPARK-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273877#comment-14273877
]
Ilya Ganelin edited comment on SPARK-2584 at 1/12/15 7:08 PM:
--------------------------------------------------------------
Understood, I am able to recreate this issue in 1.1. I'll work on a fix to
clarify what's going on. Thank.
was (Author: ilganeli):
Understood, I was looking at the UI for Spark 1.1 and did not see the block
storage level represented as MEMORY_AND_DISK or DISK_ONLY. It's now presented
as Memory Deserialized or Disk Deserialized. I'll attempt to recreate this
problem in the newer version of Spark but wanted to know if you've seen it
since 1.0.1.
> Do not mutate block storage level on the UI
> -------------------------------------------
>
> Key: SPARK-2584
> URL: https://issues.apache.org/jira/browse/SPARK-2584
> Project: Spark
> Issue Type: Bug
> Components: Spark Core, Web UI
> Affects Versions: 1.0.1
> Reporter: Andrew Or
>
> If a block is stored MEMORY_AND_DISK and we drop it from memory, it becomes
> DISK_ONLY on the UI. We should preserve the original storage level proposed
> by the user, in addition to the change in actual storage level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
