[SERVER-66377] The cluster chunks resize routine should be resilient to collection UUID changes caused by renameCollection() Created: 11/May/22 Updated: 29/Oct/23 Resolved: 16/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc6, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v6.0
|
||||||||
| Sprint: | Sharding EMEA 2022-05-16, Sharding EMEA 2022-05-30 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 130 | ||||||||
| Description |
|
It has been observed that the execution of renameCollection with dropTarget=true may cause ClusterChunksResizePolicy to hang the config server if the target collection is an existing sharded namespace that is currently being processed by the policy. The root cause of the problem is ClusterChunksResizePolicy referencing the target collection with a UUID that does not match the content of config.collections once renameCollection completes. |
| Comments |
| Comment by Githook User [ 17/May/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: (cherry picked from commit 46c54afca7f15c78a578a4941b3a765f8f4e90c7) |
| Comment by Githook User [ 16/May/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |