Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/13143
ping @devaraj-kavali for @ArtRand's comment above.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user ArtRand commented on the issue:
https://github.com/apache/spark/pull/13143
Hello @devaraj-kavali. Yes. I've been playing around with this because it's
inconvenient to clean up ZK whenever you uninstall/reinstall the Dispatcher.
The problem is that the only signal of a
Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/13143
@ArtRand I think this is still an issue which needs to be merged, do you
have any observations with this PR?
---
-
To
Github user ArtRand commented on the issue:
https://github.com/apache/spark/pull/13143
@skonto @susanxhuynh @devaraj-kavali are people still interested in this? I
was just playing around with this code to clean up ZK state.. Would be happy to
try this when I have a few cycles.
---
Github user skonto commented on the issue:
https://github.com/apache/spark/pull/13143
@ArtRand @susanxhuynh could please review this before we call for a merge?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75908/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13143
**[Test build #75908 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75908/testReport)**
for PR 13143 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13143
**[Test build #75908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75908/testReport)**
for PR 13143 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13143
**[Test build #75907 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75907/testReport)**
for PR 13143 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75907/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13143
**[Test build #75907 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75907/testReport)**
for PR 13143 at commit
Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/13143
Thanks @mgummelt for the feedback, will update the PR with the function
rewrite.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user mgummelt commented on the issue:
https://github.com/apache/spark/pull/13143
What whole function is designed poorly. We need to totally change it
instead of tacking this on. We shouldn't be calling `driver.run()` in a
separate thread. We should be calling
Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/13143
@mgummelt /@tnachen, can you have a look into this?
---
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
Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/13143
@tnachen Can you check this?
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70648/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13143
**[Test build #70648 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70648/testReport)**
for PR 13143 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13143
**[Test build #70648 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70648/testReport)**
for PR 13143 at commit
Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/13143
MesosDriver doesn't throw any exception, it just returns with the value as
Status.DRIVER_ABORTED.
```
registerLatch.await()
// propagate any error to
Github user tnachen commented on the issue:
https://github.com/apache/spark/pull/13143
Is it because MesosDriver actually threw an exception?
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13143
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59856/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13143
**[Test build #59856 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59856/consoleFull)**
for PR 13143 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13143
**[Test build #59856 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59856/consoleFull)**
for PR 13143 at commit
Github user tnachen commented on the issue:
https://github.com/apache/spark/pull/13143
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
32 matches
Mail list logo
