Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17463
Could you close this one, please? I submitted #17610 to fix the root issue.
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/17463
I think I'd close this one as I don't think it is necessarily fixing the
problem, and might mask one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17463
Hm, I'm not sure. For example, what if the error is that the context is
never stopped? maybe assert that `awaitTerminationOrTimeout` is true to also
check this? In my experience it's the streaming
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17463
@srowen It's hard to say it's because shutting down SparkContext is the
slow part, and we can improve this case by avoiding stooping SparkContext in a
separate thread.
cc @zsxwing
---
If
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17463
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/17463
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75342/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17463
**[Test build #75342 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75342/testReport)**
for PR 17463 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17463
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75340/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17463
**[Test build #75340 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75340/testReport)**
for PR 17463 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17463
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 srowen commented on the issue:
https://github.com/apache/spark/pull/17463
I'm just curious why this solves the problem? if the problem is that the
streaming context doesn't shut down or doesn't shut down quickly, then I'd
suspect that it's not because shutting down
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17463
**[Test build #75342 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75342/testReport)**
for PR 17463 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17463
**[Test build #75340 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75340/testReport)**
for PR 17463 at commit
13 matches
Mail list logo
