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

properly fix migration in mem ack aggregation #4571

Merged
merged 8 commits into from
Jul 7, 2023
Merged

properly fix migration in mem ack aggregation #4571

merged 8 commits into from
Jul 7, 2023

Conversation

wxing1292
Copy link
Contributor

@wxing1292 wxing1292 commented Jun 30, 2023

What changed?

  • Fix migration in mem ack aggregation, since sender based / receiver based aggregation cannot be unified

Why?
Correctly unify sender based & receiver based ack aggregation

How did you test it?
UT

Potential risks
N/A

Is hotfix candidate?
1.21.2

@wxing1292 wxing1292 requested a review from a team as a code owner June 30, 2023 22:52
@wxing1292 wxing1292 requested a review from yux0 June 30, 2023 23:20
wxing1292 added a commit that referenced this pull request Jul 5, 2023
Comment on lines +400 to +401
remoteClusterInfo.AckedReplicationTaskIDs[remoteShardID] = ackTaskID
remoteClusterInfo.AckedReplicationTimestamps[remoteShardID] = ackTimestamp
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One thing I am not following, why the acked task id can be used across different share ids?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for polling mode:
targer cluster's 1 poller may poll & ack on behalf of >= 1 shards, here source cluster should update all relevant shard's ack task IDs

for streaming mode:
each target shard will has its own grpc stream & update ack using reader ID (cluster ID + shard ID)

@alexshtin
Copy link
Member

Is it hotfix candidate or not? If not, remove 1.21.2 tag, if yes, please add it to description.

wxing1292 added a commit that referenced this pull request Jul 7, 2023
@wxing1292
Copy link
Contributor Author

Is it hotfix candidate or not? If not, remove 1.21.2 tag, if yes, please add it to description.

this PR is, take a look at the github tag

@wxing1292 wxing1292 enabled auto-merge (squash) July 7, 2023 22:00
@wxing1292 wxing1292 merged commit ec89a82 into temporalio:master Jul 7, 2023
@wxing1292 wxing1292 deleted the fix-migration-2 branch July 7, 2023 22:53
wxing1292 added a commit that referenced this pull request Jul 13, 2023
wxing1292 added a commit that referenced this pull request Jul 14, 2023
* Fix migration in mem ack aggregation, since sender based / receiver based aggregation cannot be unified
dnr pushed a commit that referenced this pull request Jul 21, 2023
* Fix migration in mem ack aggregation, since sender based / receiver based aggregation cannot be unified
dnr pushed a commit that referenced this pull request Jul 21, 2023
* Fix migration in mem ack aggregation, since sender based / receiver based aggregation cannot be unified
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants