You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Kousuke Saruta (Jira)" <ji...@apache.org> on 2021/09/05 22:12:00 UTC

[jira] [Resolved] (SPARK-36603) Use WeakReference over SoftReference in LevelDB to avoid retaining iterator refs

     [ https://issues.apache.org/jira/browse/SPARK-36603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kousuke Saruta resolved SPARK-36603.
------------------------------------
    Fix Version/s: 3.1.3
                   3.2.0
       Resolution: Fixed

Issue resolved in https://github.com/apache/spark/pull/33859

> Use WeakReference over SoftReference in LevelDB to avoid retaining iterator refs
> --------------------------------------------------------------------------------
>
>                 Key: SPARK-36603
>                 URL: https://issues.apache.org/jira/browse/SPARK-36603
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 3.1.2
>            Reporter: Sean R. Owen
>            Assignee: Sean R. Owen
>            Priority: Minor
>             Fix For: 3.2.0, 3.1.3
>
>
> See discussion at https://github.com/apache/spark/pull/28769#issuecomment-906722390
> The SoftReference used to track iterators in LevelDB can prevent them from being GCed early enough, thus finalized and closed. A WeakReference would be more readily collected, and solves an apparent actual issue running a 3.1.x SHS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org