[SERVER-63086] Remove refresh of the routing table during a rename operation Created: 28/Jan/22  Updated: 29/Oct/23  Resolved: 07/Feb/22

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21
Participants:

 Description   

We can remove this piece of code from the rename operation. It was added to solve some problems related to the long names support project, but it was not enough (SERVER-62700). 

My proposal is to remove this code and to decide which kind of filtering information we want to leave on the shards before releasing the critical section. Right now I believe the rename operation leaves the filtering information as UNKNOWN, which is fine and will force to the next operation on the shard to recover the shard version. Another approach would be to call to the forceShardFilteringMetadataRefresh to end up having the right shard version before releasing the critical section.

Note that calling to onShardVersionMismatch will not work because the rename operation is holding the critical section.



 Comments   
Comment by Githook User [ 07/Feb/22 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-63086 Remove refresh of the routing table during a rename operation
Branch: master
https://github.com/mongodb/mongo/commit/ab5508ea955f5b18521e0298a722535d153fb420

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