[SERVER-36643] Figure out mixed version replication for config.transactions Created: 14/Aug/18  Updated: 27/Oct/23  Resolved: 08/Nov/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-36641 Change updates to config.transactions... Closed
is related to SERVER-36498 Remove 'config.transactions' entries ... Closed
Assigned Teams:
Sharding
Participants:

 Description   

In v4.0 secondary replication updates for config.transactions are expressed as replacement updates. This can be an issue for v4.0 secondaries when trying to replicate an oplog history that contains writes for newer versions since the replacement updates can accidentally remove fields that was not included in the replacement update request.



 Comments   
Comment by Judah Schvimer [ 05/Nov/18 ]

Tickets such as SERVER-36498 account for the upgrade-downgrade logic required for prepare. This ticket was originally created when the coordinator was going to make use of 'config.transactions' in new ways beyond what prepare had planned, and thus potentially needed its own upgrade-downgrade logic. If the cross-shard transactions project no longer is changing the 'config.transactions' table, then this ticket is "Gone Away".

Comment by Esha Maharishi (Inactive) [ 05/Nov/18 ]

Ok. I believe the prepare team has already tracked this work in their own tickets. judah.schvimer, is that right? If so, we will close it as a duplicate.

Comment by Randolph Tan [ 05/Nov/18 ]

esha.maharishi it could be either.

Comment by Esha Maharishi (Inactive) [ 05/Nov/18 ]

renctan, should this work be on the prepare team?

Generated at Thu Feb 08 04:43:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.