Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-54695016
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19870/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-54698316
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19870/consoleFull)
for PR 2056 at commit
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-54699362
@witgo Thanks for looking into this bug, but I think this patch is not
necessary anymore. So mind closing this PR?
---
If your project is set up for it, you can reply to
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/2056
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53782725
@andrewor14 and I looked into and increasing timeout does solve SPARK-3015.
Well the real reason is still unknown. All we know is that once in a while,
when the executor
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53534681
This was fixed by a different approach in #2143.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53544987
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19302/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53545458
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19303/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53545805
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19303/consoleFull)
for PR 2056 at commit
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53546333
@tdas @pwendell We do not need to wait for clear `RDD`,`Broadcast`
#2143 does not solve the timeout in [removeShuffle
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53546851
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19304/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53547767
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19304/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53548341
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19305/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53550225
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19302/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53552535
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19305/consoleFull)
for PR 2056 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53611161
@witgo removing RDDs and broadcasts are different because there are much
fewer blocks. If shuffle consolidation is not enabled, shuffle blocks may
indeed take a long
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53664268
Increase the timeout in [removeBroadcast
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53469866
This could be an acceptable solution, but we dont know whether 10 * default
akka timeout is a good threshold either. The error is happening because we made
the
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53483416
This is a implementation that I was thinking of. Hopefully this will solve
the issues you are seeing.
https://github.com/apache/spark/pull/2143
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53149761
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19106/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53150684
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19107/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53150822
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19106/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-53151891
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19107/consoleFull)
for PR 2056 at commit
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/2056
[SPARK-3139] Akka timeouts from ContextCleaner when cleaning shuffles
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-3139
24 matches
Mail list logo
