Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Replication
Confidence Status:
None
Work Order:
3

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

After this ticket there should be NO areas of code that take the RSTL when the feature flag is enabled. This will involve also adding feature flag checks to places that invariant isRstlLocked to see if we have an intent declared instead, and adding an invariant inside of ReplicationStateTransitionLockGuard.

This will involve fixing places where isRSTLLocked is currently called (either removing them or replacing with an equivalent check against intents)

depends on

SERVER-102622 Handle explicit uses of ReplicationStateTransitionLockGuard

Backlog

SERVER-102624 Change any explicit uses of resourceIdReplicationStateTransitionLock

Backlog

SERVER-104961 Use transactions intent for intent registry in transaction_participant

Backlog

SERVER-102621 Make Replication state transitions use IntentRegistry

In Code Review

SERVER-102623 Replace automatic RSTL acquisitions with Intents

In Progress

is duplicated by

SERVER-104369 Disable RSTL acquisitions under IntentRegistration featureFlag

Closed

(1 is duplicated by)

Assignee:: Unassigned
Reporter:: Sean Zimmerman
Participants:: Sean Zimmerman
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Apr 09 2025 07:51:49 PM UTC
Updated:: May 08 2025 09:28:35 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates