-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ClusterScalability Jun9-Jun23
-
200
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In ReshardingOplogFetcherTest for some reason sometimes a ReshardingOplogFetcher is accessed after the test is finished.
This is hard to reproduce. I was able to reproduce it around 10% of the times, but only when:
1. Compiling with --config=dbg_aubsan
2. Running `stress -c <number of CPUs>` in parallel with the test.
This looks like a purely testing problem.
Stack trace and logs are attached
- is related to
-
SERVER-103554 Make ReshardingOplogFetcher fetch oplog entries from the primary during the critical section
-
- Closed
-
-
SERVER-105842 Make ReshardingOplogFetcher fetch oplog entries from the primary when the recipient is approaching strict consistency to prepare for the critical section
-
- Closed
-
-
SERVER-105927 Update ReshardingOplogFetcher::_reschedule to use AsyncTry
-
- Closed
-