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-22429][STREAMING] Streaming checkpointing code does not retry after failure #19645

Closed
wants to merge 1 commit into from

Conversation

tmgstevens
Copy link

@tmgstevens tmgstevens commented Nov 2, 2017

What changes were proposed in this pull request?

SPARK-14930/SPARK-13693 put in a change to set the fs object to null after a failure, however the retry loop does not include initialization. Moved fs initialization inside the retry while loop to aid recoverability.

How was this patch tested?

Passes all existing unit tests.

@srowen
Copy link
Member

srowen commented Nov 3, 2017

Looks good though this would have to be opened vs master. How about just not nulling fs? Rather than reopen it.

@tmgstevens tmgstevens changed the base branch from branch-2.2 to master November 3, 2017 11:04
@tmgstevens
Copy link
Author

@srowen, okay my issue around compilation issues, so I've changed the base branch.

We can not null it, but I guess by re-open it we stand a better chance of resolving any unexpected errors. That logic was put in deliberately as part of e7b62cb a few years ago now.

@SparkQA
Copy link

SparkQA commented Nov 3, 2017

Test build #3978 has finished for PR 19645 at commit 8ce4c1c.

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

asfgit pushed a commit that referenced this pull request Nov 5, 2017
…after failure

## What changes were proposed in this pull request?

SPARK-14930/SPARK-13693 put in a change to set the fs object to null after a failure, however the retry loop does not include initialization. Moved fs initialization inside the retry while loop to aid recoverability.

## How was this patch tested?

Passes all existing unit tests.

Author: Tristan Stevens <tristan@cloudera.com>

Closes #19645 from tmgstevens/SPARK-22429.

(cherry picked from commit fe258a7)
Signed-off-by: Sean Owen <sowen@cloudera.com>
asfgit pushed a commit that referenced this pull request Nov 5, 2017
…after failure

## What changes were proposed in this pull request?

SPARK-14930/SPARK-13693 put in a change to set the fs object to null after a failure, however the retry loop does not include initialization. Moved fs initialization inside the retry while loop to aid recoverability.

## How was this patch tested?

Passes all existing unit tests.

Author: Tristan Stevens <tristan@cloudera.com>

Closes #19645 from tmgstevens/SPARK-22429.

(cherry picked from commit fe258a7)
Signed-off-by: Sean Owen <sowen@cloudera.com>
@srowen
Copy link
Member

srowen commented Nov 5, 2017

Merged to master/2.2/2.1. Let me know if there's a case to backport further.

@asfgit asfgit closed this in fe258a7 Nov 5, 2017
MatthewRBruce pushed a commit to Shopify/spark that referenced this pull request Jul 31, 2018
…after failure

## What changes were proposed in this pull request?

SPARK-14930/SPARK-13693 put in a change to set the fs object to null after a failure, however the retry loop does not include initialization. Moved fs initialization inside the retry while loop to aid recoverability.

## How was this patch tested?

Passes all existing unit tests.

Author: Tristan Stevens <tristan@cloudera.com>

Closes apache#19645 from tmgstevens/SPARK-22429.

(cherry picked from commit fe258a7)
Signed-off-by: Sean Owen <sowen@cloudera.com>
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.

3 participants