[SERVER-61337] ConvertToCapped should check versioning Created: 09/Nov/21 Updated: 29/Oct/23 Resolved: 02/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| 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 | ||||
| Participants: | |||||
| Linked BF Score: | 20 | ||||
| Description |
|
TheĀ ConvertToCapped command should not be run on sharded collections. But the command on an unsharded collection does not check for collection version from the mongos before executing the command. This can cause the command to be executed on a sharded cluster if sent from a stale mongos that doesn't know the collection is sharded. We should add a check in this command on the shard to ensure it does not run from a mongos with a stale collection version. |
| Comments |
| Comment by Githook User [ 02/Dec/21 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |