-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
ALL
-
Repl 2025-09-15, Repl 2025-09-29
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
During step-up, we do finds on several tables including config.transactions. If these tables are being validated at the time, the find will fail with EBUSY, which we do not handle. Probably the easiest way to avoid this is to take an IS lock on the table; we don't need the utmost performance when doing these operations.
- is related to
-
SERVER-97174 validate command on secondaries reads unfinished oplog batch
-
- Closed
-
-
SERVER-109658 Investigate if we need to add concurrency control to the oplogApplier's empty batch logic when full validation is concurrently running
-
- Closed
-
-
SERVER-111044 Catch EBUSY errors in a retry loop on find operations
-
- Needs Scheduling
-