[SERVER-42788] For convertToCapped, router should not check if the collection is sharded itself Created: 13/Aug/19 Updated: 06/Dec/22 Resolved: 16/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Currently the router checks its cache to see if the collection is sharded, and fails the convertToCapped operation if so. This is incorrect because the router's cache might be stale. Instead, the router should rely on the shard to check whether the collection is sharded. The router already attaches shardVersion, but the shard should actually check the shardVersion, which it does not currently do. |
| Comments |
| Comment by Ratika Gandhi [ 16/Aug/19 ] |
|
Known behavior. won't fix. |