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

Implement tiered replication stream receiver #5856

Merged
merged 15 commits into from May 14, 2024

Conversation

xwduan
Copy link
Contributor

@xwduan xwduan commented May 6, 2024

What changed?

Implement tiered replication stream receiver:

  1. Change receiver.receive to handle original (single ACK level) and new (prioritized ACK level) properly
  2. Change receiver.ACK to properly ACK back to sender with proper ACK level.

Why?

To prioritize different category of replication tasks.

How did you test it?

integration test.

Potential risks

Replication stack will go down.

Documentation

n/a

Is hotfix candidate?

no

service/history/replication/fx.go Show resolved Hide resolved
service/history/replication/stream_receiver.go Outdated Show resolved Hide resolved
service/history/replication/stream_receiver.go Outdated Show resolved Hide resolved
@xwduan xwduan marked this pull request as ready for review May 7, 2024 17:02
@xwduan xwduan requested a review from a team as a code owner May 7, 2024 17:02
@xwduan xwduan enabled auto-merge (squash) May 14, 2024 17:17
@xwduan xwduan merged commit 7423404 into main May 14, 2024
42 checks passed
@xwduan xwduan deleted the willduan/tiered_replication_receiver branch May 14, 2024 18:50
ychebotarev pushed a commit to ychebotarev/temporal that referenced this pull request May 16, 2024
## What changed?
<!-- Describe what has changed in this PR -->
Implement tiered replication stream receiver:
1. Change `receiver.receive` to handle original (single ACK level) and
new (prioritized ACK level) properly
2. Change `receiver.ACK` to properly ACK back to sender with proper ACK
level.
## Why?
<!-- Tell your future self why have you made these changes -->
To prioritize different category of replication tasks.
## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
integration test.
## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
Replication stack will go down.
## 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.

None yet

3 participants