[SERVER-82066] Handle direct connections for implicit creation path Created: 11/Oct/23  Updated: 07/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: PM-3364-Milestone-5
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-83214 Handle direct connection database and... Backlog
Assigned Teams:
Catalog and Routing
Sprint: Sharding EMEA 2023-10-30
Participants:

 Description   

In SERVER-80372, the checks for taking the ScopedAllowImplicitCollectionCreate_UNSAFE are using ShardingState::get(opCtx)->isComingFromRouter to determine whether a connection is a direct shard connection and so should be allowed to create a local (untracked) collection.

This isn't a good way to check for direct connections because it will also return false during ddl operations, for example. This ticket is to update the check in the scoped acquisitions to correctly check for direct connections.


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