[SERVER-57322] Invalidate filtering info on participants at the end of renameCollection Created: 01/Jun/21  Updated: 29/Oct/23  Resolved: 03/Jun/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.0.0-rc0
Fix Version/s: 5.0.0-rc1, 5.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-06-14
Participants:
Linked BF Score: 46

 Description   

Upon finishing a rename, there is currently no filtering metadata refresh (e.g like we do in createCollectionCoordinator). This can lead to a situation where, after renaming a sharded collection, the 'toNss' filtering metadata is incorrectly left as 'unsharded'.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 03/Jun/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-57322 Invalidate filtering info on participants at the end of renameCollection
Branch: v5.0
https://github.com/mongodb/mongo/commit/ef58ce33f5c685a85b6da5069efca144c78e49ce

Comment by Githook User [ 03/Jun/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-57322 Invalidate filtering info on participants at the end of renameCollection
Branch: master
https://github.com/mongodb/mongo/commit/f06bafc144c77c73b273652fc41ce50b7e97cee9

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