[SERVER-82074] Refactor collection creation idempotency to use single collection acquisition Created: 11/Oct/23 Updated: 23/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | car-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||
| Participants: | |||||||||||||
| Story Points: | 2 | ||||||||||||
| Description |
|
Currently, the mechanism that provides idempotency for creating a collection acquires the collection to check its options after receiving a NamespaceExists error from the creation attempt. This means that there are two separate acquisitions that occur: once to try to create the collection, and once to check if the existing options are the same (with the collection being released in between). We may want to refactor this so that all of this can happen under a single collection acquisition. |