[
https://issues.apache.org/jira/browse/SPARK-16440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384131#comment-15384131
]
Sean Owen commented on SPARK-16440:
-----------------------------------
Yeah it seems good to destroy even in case of errors, but in practice, an error
here means lots of things are wrong. Actually using try-finally to destroy
every RDD/variable would make the code a mess. I think many cases where it
plausibly won't matter, we don't. If there's a decent argument that errors here
are common for some reason, OK, but not sure that's true.
> Undeleted broadcast variables in Word2Vec causing OoM for long runs
> --------------------------------------------------------------------
>
> Key: SPARK-16440
> URL: https://issues.apache.org/jira/browse/SPARK-16440
> Project: Spark
> Issue Type: Bug
> Components: MLlib
> Affects Versions: 1.6.0, 1.6.1, 1.6.2, 2.0.0
> Reporter: Anthony Truchet
> Assignee: Sean Owen
> Fix For: 1.6.3, 2.0.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Three broadcast variables created at the beginning of {{Word2Vec.fit()}} are
> never deleted nor unpersisted. This seems to cause excessive memory
> consumption on the driver for a job running hundreds of successive training.
> They are
> {code}
> val expTable = sc.broadcast(createExpTable())
> val bcVocab = sc.broadcast(vocab)
> val bcVocabHash = sc.broadcast(vocabHash)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
