Uh oh!
There was an error while loading. Please reload this page.
[BEAM-6733] Add pipeline option to flush bundle data before checkpointing - #11678
Merged
Conversation
mxm
commented
May 12, 2020
ContributorAuthor
Run Python Load Tests ParDo Flink Streaming |
1 similar comment
mxm
commented
May 12, 2020
ContributorAuthor
Run Python Load Tests ParDo Flink Streaming |
mxm
commented
May 15, 2020
ContributorAuthor
Had to rebase due to merge conflicts with the new website. |
mxm
commented
May 15, 2020
ContributorAuthor
Run Python Load Tests ParDo Flink Streaming |
mxm
commented
May 15, 2020
ContributorAuthor
Based on the load test results, I'm not changing the default behavior here. Instead, flushing the bundle output before a checkpoint can be turned on optionally. |
…ting We had a couple of PRs in which we wanted to remove the buffering of bundle output during checkpointing: apache#7940apache#9652. Ultimately, we didn't merge any of those because we weren't sure how the change would affect the checkpoint performance. As a better migration path, this introduces a pipeline option to change the default, buffering bundle output during checkpointing, to finishing the bundle and flushing all data before checkpointing.
mxm
commented
May 18, 2020
ContributorAuthor
Run Python2_PVR_Flink PreCommit |
mxm
commented
May 18, 2020
ContributorAuthor
After more test runs, it looks like the effect of finishing the bundle before the checkpoint is marginal / non-existent. However, we will have to run more experiments to change it to be the default. The option will be useful for the testing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We had a couple of PRs in which we wanted to remove the buffering of bundle
output during checkpointing: #7940#9652. Ultimately, we didn't merge any of
those because we weren't sure how the change would affect the checkpoint
performance.
As a better migration path, this introduces a pipeline option to change the
default, buffering bundle output during checkpointing, to finishing the bundle
and flushing all data before checkpointing.
Post-Commit Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.