[
https://issues.apache.org/jira/browse/SPARK-10787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934292#comment-14934292
]
Ted Yu commented on SPARK-10787:
--------------------------------
I can think of two approaches:
1. Cloning ObjectOutputStream using weak references. We need to consider
license. Also, ObjectOutputStream may reference Java internal methods / fields.
This makes maintaining the clone difficult.
2. Switch to Kryo-based serialization.
> Reset ObjectOutputStream more often to prevent OOME
> ---------------------------------------------------
>
> Key: SPARK-10787
> URL: https://issues.apache.org/jira/browse/SPARK-10787
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Ted Yu
> Priority: Minor
>
> In the thread, Spark ClosureCleaner or java serializer OOM when trying to
> grow (http://search-hadoop.com/m/q3RTtAr5X543dNn), Jay Luan reported that
> ClosureCleaner#ensureSerializable() resulted in OOME.
> The cause was that ObjectOutputStream keeps a strong reference of every
> object that was written to it.
> This issue tries to avoid OOME by calling reset() more often.
--
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
