You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "David C Navas (JIRA)" <ji...@apache.org> on 2019/05/21 18:11:00 UTC
[jira] [Resolved] (SPARK-27728) Address thread-safety of
InMemoryStore and ElementTrackingStores.
[ https://issues.apache.org/jira/browse/SPARK-27728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David C Navas resolved SPARK-27728.
-----------------------------------
Resolution: Duplicate
Fix Version/s: 3.0.0
Resolved in umbrella ticket
> Address thread-safety of InMemoryStore and ElementTrackingStores.
> -----------------------------------------------------------------
>
> Key: SPARK-27728
> URL: https://issues.apache.org/jira/browse/SPARK-27728
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 2.3.3
> Reporter: David C Navas
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: RaceConditions.pdf
>
>
> There are a couple of thread-safety issues we discovered in trying to track down excessive memory use. These are detailed in the attachment. One is a problem that looks like it might be a race condition in the ordering of updating elements in the tracking store, and the other is an incorrect (and likely unnecessary) caching of the size of an underlying data-structure.
>
--
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