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

Handle Buffered Events when replicating #6919

Merged
merged 3 commits into from
Dec 3, 2024

Conversation

xwduan
Copy link
Contributor

@xwduan xwduan commented Dec 2, 2024

What changed?

  1. Skip converting task when mutable state has buffered events
  2. Skip replication task when sync state and source mutable state has buffered event

Why?

Buffered events will cause in consistent state if we replicate state without events

How did you test it?

unit test

Potential risks

no risk, not enabled

Documentation

n/a

Is hotfix candidate?

no

@xwduan xwduan marked this pull request as ready for review December 2, 2024 23:05
@xwduan xwduan requested a review from a team as a code owner December 2, 2024 23:05
@xwduan xwduan enabled auto-merge (squash) December 3, 2024 18:30
@xwduan xwduan merged commit ee5b38d into main Dec 3, 2024
49 checks passed
@xwduan xwduan deleted the willduan/fix_replication_task_converter branch December 3, 2024 19:07
xwduan added a commit that referenced this pull request Dec 3, 2024
## What changed?
<!-- Describe what has changed in this PR -->
1. Skip converting task when mutable state has buffered events
2. Skip replication task when sync state and source mutable state has
buffered event
## Why?
<!-- Tell your future self why have you made these changes -->
Buffered events will cause in consistent state if we replicate state
without events
## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
unit test
## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
no risk, not enabled
## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->
n/a
## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
no
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