[SERVER-53384] Enclose sharded collection metadata rename logic in a transaction Created: 16/Dec/20  Updated: 29/Oct/23  Resolved: 22/Dec/20

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-12-28
Participants:

 Description   

As part of the rename flow for sharded collections, the primary shard will issue on the CSRS a transaction enclosing the following operations:

  • Update config.collections entry: change nss and epoch (it is actually needed to delete/recreate the document since the namespace is saved in the immutable _id field).
  • Update config.chunks entries: change epoch/timestamp (no need to consider the nss field: it's thrown out under SERVER_53105 and rename will just happen with stable FCV)


 Comments   
Comment by Ian Whalen (Inactive) [ 04/Jan/21 ]

Author:

{'username': u'evrg-bot-webhook', 'name': u'Pierlauro Sciarelli', 'email': u'pierlauro.sciarelli@mongodb.com'}

Message:SERVER-53384 Enclose sharded collection metadata rename logic in a transaction
Branch:master
https://github.com/mongodb/mongo/commit/3f5579f4223b6b94127475c897156eb0a1cefe5c

Comment by Pierlauro Sciarelli [ 22/Dec/20 ]

Commit URI. Manually commenting because the Github-Jira hook didn't work for some reason.

Generated at Thu Feb 08 05:30:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.