You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2018/02/28 15:18:00 UTC

[jira] [Resolved] (SPARK-23508) blockManagerIdCache in BlockManagerId may cause oom

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

Wenchen Fan resolved SPARK-23508.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.1
                   2.4.0
                   2.2.2

Issue resolved by pull request 20667
[https://github.com/apache/spark/pull/20667]

> blockManagerIdCache in BlockManagerId may cause oom
> ---------------------------------------------------
>
>                 Key: SPARK-23508
>                 URL: https://issues.apache.org/jira/browse/SPARK-23508
>             Project: Spark
>          Issue Type: Bug
>          Components: Deploy, Spark Core
>    Affects Versions: 2.1.1, 2.2.1
>            Reporter: zhoukang
>            Assignee: zhoukang
>            Priority: Major
>             Fix For: 2.2.2, 2.4.0, 2.3.1
>
>         Attachments: elepahnt-oom1.png, elephant-oom.png
>
>
> blockManagerIdCache in BlockManagerId will not remove old values which may cause oom
> {code:java}
> val blockManagerIdCache = new ConcurrentHashMap[BlockManagerId, BlockManagerId]()
> {code}
> Since whenever we apply a new BlockManagerId, it will put into this map.
> below is an jmap:
> !elepahnt-oom1.png!
> !elephant-oom.png!



--
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