[SERVER-82072] Time-series collection creation does not perform shard version checks on buckets collection Created: 11/Oct/23  Updated: 17/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-80776 create fails on already-sharded time-... Closed
is related to SERVER-82074 Refactor collection creation idempote... Backlog
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Creating a time-series collection on a sharded cluster forwards the command to the primary shard using the user-facing view namespace (which is inherently unsharded), meaning that even if a sharded buckets collection already exists that shard versioning information is not included in the request. When creating the buckets collection on the shard, we skip shard versions checks when acquiring the collection and then return early if the collection already exists on that shard. There is a shard version check after that, but at that point we already know that the collection doesn't exist on the shard (plus the shard version information provided with the request is for a different namespace, as previously noted).


Generated at Thu Feb 08 06:48:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.