Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- car-investigation

Assigned Teams:

Catalog and Routing
CAR Domain/s:

🟥 DDL

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

ConvertToCappedCoordinator and RefineCollectionShardKeyCoordinator use ParticipantCausalityBarrier instead of the simpler and more common AllShardsAndConfigCausalityBarrier.

Consider if it's acceptable to simplify this by using AllShardsAndConfigCausalityBarrier everywhere instead.

See also this comment for more context.

depends on

SERVER-120986 Extract OperationSessionInfo logic into shared coordinator utility

Closed

is depended on by

SERVER-121798 Consider if causality barriers can be managed by base classes

Blocked

is related to

SERVER-123498 Add OSI causality barrier on resharding coordinator step-up

Closed

Assignee:: Unassigned
Reporter:: Brett Nawrocki
Participants:: Brett Nawrocki
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Mar 16 2026 09:52:07 PM UTC
Updated:: Apr 24 2026 06:10:04 PM UTC