-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ALL
-
200
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
resharding_critical_section_repl_lag.js halts replication on select nodes to verify that the resharding critical section accounts for replication lag on donors and recipients. During oplog fetching, the resharding recipient's aggregation uses the "nearest" readPreference, which may target a node that hasn't restarted replication. The test restarts the node after the resharding operation is expected to succeed, causing the recipient to hang waiting for the finalReshard oplog. More details in BF-37887.
- is related to
-
SERVER-105842 Make ReshardingOplogFetcher fetch oplog entries from the primary when the recipient is approaching strict consistency to prepare for the critical section
-
- Closed
-