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.

Sign up for GitHub

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

Jump to bottom

[doc] WAL behaviors when pipelines stop and then resume #383

Open
xdevxy opened this issue Nov 22, 2022 · 0 comments
Open

[doc] WAL behaviors when pipelines stop and then resume #383

xdevxy opened this issue Nov 22, 2022 · 0 comments
Labels
area/reduce Reduce operations like GroupByKey documentation Improvements or additions to documentation enhancement New feature or request

Comments

@xdevxy
Copy link
Contributor

xdevxy commented Nov 22, 2022 •
edited
Loading

Summary

For a pipeline that stop and then resume, the data for the last batch of window after being paused may not be triggered and leaving uncleaned state in the PBQ WAL. This is expected, but we need to document the behavior so user won't be confused.

Use Cases

Pipeline pause or system upgrade.

Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
@xdevxy xdevxy added enhancement New feature or request area/reduce Reduce operations like GroupByKey documentation Improvements or additions to documentation labels Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/reduce Reduce operations like GroupByKey documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xdevxy