-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:None
-
Replication
-
ALL
On primaries, we handle speculative transactions by waiting for the read op time to become majority committed by treating it as a write op time when we commit the transaction with write concern majority.
On secondaries, this doesn't work. If we wait for write concern on secondaries, we get a "stepped down" error. We either need to special-case read-only transactions so they can use a write concern on secondaries, or find another mechanism to wait.