[
https://issues.apache.org/jira/browse/SPARK-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380653#comment-15380653
]
Michał Wesołowski edited comment on SPARK-5484 at 7/16/16 9:34 AM:
-------------------------------------------------------------------
[~ankurd] do you plan to prepare another solution? I could see your pull
request was closed, but did solve problem and was best thing at a time. The
only thing I could see lacking was no ckeckpoint directory cleaning, and I
guess I would change checkpoint iterations to 35 since it worked better during
my tests.
More general solution proposed within SPARK-5561 needs a change within
PeriodicRDDCheckpointer and PeriodicGraphCheckpointer - either to move it from
mllib or change access modifier.
was (Author: wesolows):
[~ankurd] do you plan to prepare another solution? I could see your pull
request was closed, but did solve problem and was best thing at a time. The
only thing I could see lacking was no ckeckpoint directory cleaning, and I
guess I would change checkpoint iterations to 35 since it worked better during
my tests.
More general solution proposed within [Spark-5561] needs a change within
PeriodicRDDCheckpointer and PeriodicGraphCheckpointer - either to move it from
mllib or change access modifier.
> Pregel should checkpoint periodically to avoid StackOverflowError
> -----------------------------------------------------------------
>
> Key: SPARK-5484
> URL: https://issues.apache.org/jira/browse/SPARK-5484
> Project: Spark
> Issue Type: Bug
> Components: GraphX
> Reporter: Ankur Dave
> Assignee: Ankur Dave
>
> Pregel-based iterative algorithms with more than ~50 iterations begin to slow
> down and eventually fail with a StackOverflowError due to Spark's lack of
> support for long lineage chains. Instead, Pregel should checkpoint the graph
> periodically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
