[SERVER-59810] mongos may see the timeseries collection as unsharded after shardCollection command Created: 07/Sep/21 Updated: 13/Oct/21 Resolved: 26/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rui Liu | Assignee: | Arun Banala |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||
| Sprint: | QE 2021-10-04 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When a mongos has stale config information, it may think a timeseries collection is unsharded, but it's actually sharded. In this case, the mongos will attach the shard version to the view namespace (through the logic of ChunkManagerTargeter) instead of bucket namespace. We should check if mongod will successfully detect this case and throws StaleConfig exception back to mongos. |
| Comments |
| Comment by Arun Banala [ 26/Sep/21 ] |
|
This issue is being addressed as part of |