Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-20131][DStream][Test] Flaky Test: org.apache.spark.streaming.StreamingContextSuite #17463

Closed
wants to merge 2 commits into from

Conversation

uncleGen
Copy link
Contributor

@uncleGen uncleGen commented Mar 29, 2017

What changes were proposed in this pull request?

do not stop the SparkContext in another separate thread.

How was this patch tested?

Jenkins.

@srowen
Copy link
Member

srowen commented Mar 29, 2017

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 SparkContext is the slow part, but I'm not sure.

@SparkQA
Copy link

SparkQA commented Mar 29, 2017

Test build #75340 has finished for PR 17463 at commit 89d1d35.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Mar 29, 2017

Test build #75342 has finished for PR 17463 at commit c68c285.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@uncleGen
Copy link
Contributor Author

uncleGen commented Apr 1, 2017

@srowen It's hard to say it's because shutting down SparkContext is the slow part, and we can improve this case by avoiding stopping SparkContext in a separate thread.
cc @zsxwing

@srowen
Copy link
Member

srowen commented Apr 1, 2017

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 context that can take a while to stop because it has to wait for batches. It's not 'graceful' in this test though, but I've certainly seen it fail to stop quickly.

@srowen
Copy link
Member

srowen commented Apr 7, 2017

I think I'd close this one as I don't think it is necessarily fixing the problem, and might mask one.

@zsxwing
Copy link
Member

zsxwing commented Apr 11, 2017

Could you close this one, please? I submitted #17610 to fix the root issue.

@maropu maropu mentioned this pull request Apr 23, 2017
maropu added a commit to maropu/spark that referenced this pull request Apr 23, 2017
@uncleGen uncleGen closed this Apr 24, 2017
asfgit pushed a commit that referenced this pull request Apr 24, 2017
## What changes were proposed in this pull request?
This pr proposed to close stale PRs. Currently, we have 400+ open PRs and there are some stale PRs whose JIRA tickets have been already closed and whose JIRA tickets does not exist (also, they seem not to be minor issues).

// Open PRs whose JIRA tickets have been already closed
Closes #11785
Closes #13027
Closes #13614
Closes #13761
Closes #15197
Closes #14006
Closes #12576
Closes #15447
Closes #13259
Closes #15616
Closes #14473
Closes #16638
Closes #16146
Closes #17269
Closes #17313
Closes #17418
Closes #17485
Closes #17551
Closes #17463
Closes #17625

// Open PRs whose JIRA tickets does not exist and they are not minor issues
Closes #10739
Closes #15193
Closes #15344
Closes #14804
Closes #16993
Closes #17040
Closes #15180
Closes #17238

## How was this patch tested?
N/A

Author: Takeshi Yamamuro <yamamuro@apache.org>

Closes #17734 from maropu/resolved_pr.
peter-toth pushed a commit to peter-toth/spark that referenced this pull request Oct 6, 2018
This pr proposed to close stale PRs. Currently, we have 400+ open PRs and there are some stale PRs whose JIRA tickets have been already closed and whose JIRA tickets does not exist (also, they seem not to be minor issues).

// Open PRs whose JIRA tickets have been already closed
Closes apache#11785
Closes apache#13027
Closes apache#13614
Closes apache#13761
Closes apache#15197
Closes apache#14006
Closes apache#12576
Closes apache#15447
Closes apache#13259
Closes apache#15616
Closes apache#14473
Closes apache#16638
Closes apache#16146
Closes apache#17269
Closes apache#17313
Closes apache#17418
Closes apache#17485
Closes apache#17551
Closes apache#17463
Closes apache#17625

// Open PRs whose JIRA tickets does not exist and they are not minor issues
Closes apache#10739
Closes apache#15193
Closes apache#15344
Closes apache#14804
Closes apache#16993
Closes apache#17040
Closes apache#15180
Closes apache#17238

N/A

Author: Takeshi Yamamuro <yamamuro@apache.org>

Closes apache#17734 from maropu/resolved_pr.

Change-Id: Id2e590aa7283fe5ac01424d30a40df06da6098b5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants