[SERVER-83875] Simplify flow for creating collection in a transaction on sharded clusters Created: 05/Dec/23 Updated: 06/Dec/23 |
|
| Status: | Blocked |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Due to some current limitations of the transaction machinery, SERVER-81937 is going to introduce a very complex flow with additional hops between router and shards to support the atomic creation of a collection entry on local+sharding catalog. Purpose of this ticket is to simplify such flow and get rid of additional hops once the transaction machinery will support adding participants from a shard and writing directly shard-to-shard without having to pass by the router. |