[SERVER-85182] Sharded timeseries collections - any queries with readConcern: "available" hang indefinitely Created: 12/Jan/24 Updated: 07/Feb/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.12, 7.0.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shane Smith | Assignee: | Sergi Mateo Bellido |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | Sharding, time-series | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||
| Assigned Teams: |
Catalog and Routing
|
||||||
| Operating System: | ALL | ||||||
| Steps To Reproduce: | 1. Start a sharded cluster on one of the latest MongoDB releases (i.e. 7.0.5, 6.0.12 - older releases also seem to exhibit this behavior from checking a couple others) 2. Enable sharding
3. Insert a few sample docs
4. Attempt to query the sharded timeseries collection in some way specifying readConcern: "available" and the operation will hang indefinitely. Any other readConcern level seems to work fine.
|
||||||
| Sprint: | Repl 2024-02-05, CAR Team 2024-02-19 | ||||||
| Participants: | |||||||
| Case: | (copied to CRM) |
| Description |
|
Any queries with readConcern: "available" will hang indefinitely on a sharded timeseries collection, while all other readConcern levels execute the same query successfully. |