You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 05:37:41 UTC
[jira] [Resolved] (SPARK-5077) Map output statuses can still exceed
spark.akka.frameSize
[ https://issues.apache.org/jira/browse/SPARK-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-5077.
---------------------------------
Resolution: Incomplete
> Map output statuses can still exceed spark.akka.frameSize
> ---------------------------------------------------------
>
> Key: SPARK-5077
> URL: https://issues.apache.org/jira/browse/SPARK-5077
> Project: Spark
> Issue Type: Bug
> Components: Shuffle
> Affects Versions: 1.2.0, 1.3.0, 1.4.1
> Reporter: Josh Rosen
> Priority: Major
> Labels: bulk-closed
>
> Since HighlyCompressedMapOutputStatuses uses a bitmap for tracking empty blocks, its size is not bounded and thus Spark is still susceptible to "MapOutputTrackerMasterActor: Map output statuses
> were 11141547 bytes which exceeds spark.akka.frameSize"-type errors, even in 1.2.0.
> We needed to use a bitmap for tracking zero-sized blocks (see SPARK-3740; this isn't just a performance issue; it's necessary for correctness). This will require a bit more effort to fix, since we'll either have to find a way to use a fixed size / capped size encoding for MapOutputStatuses (which might require changes to let us fetch empty blocks safely) or figure out some other strategy for shipping these statues.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org