Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15267
Hi @ashwinshankar77, if you are not currently able to work on this further,
maybe it should be closed for now. It seems inactive for few months.
---
If your project is set up for it, you can re
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15267
@ashwinshankar77 do you plan on updating this and removing the "WIP"?
---
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 d
Github user ashwinshankar77 commented on the issue:
https://github.com/apache/spark/pull/15267
Thanks for the review @tgravescs! I'll update the patch shortly. We are
also trying out SPARK-17365.
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/15267
It looks like you should be able to remove it after the
context.reply(ExecutorKilled) return. The killExecutors should be called
before the loss reason and if there is a race there its just going
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/15267
SPARK-17365 should help with this situation have you tried that?
overall the approach seems ok to me. Its an easy short cut to prevent
asking if we already know. There is the possible rac
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15267
Merged build finished. Test PASSed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15267
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66015/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15267
**[Test build #66015 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66015/consoleFull)**
for PR 15267 at commit
[`859718c`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15267
**[Test build #66015 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66015/consoleFull)**
for PR 15267 at commit
[`859718c`](https://github.com/apache/spark/commit/8
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15267
ok to test
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15267
Can one of the admins verify this patch?
---
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 feat
11 matches
Mail list logo
