-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding NYC 2022-05-16, Sharding NYC 2022-05-30
-
0
-
1
As seen in BF-23933, it sometimes takes a long time for a replica set member to fully transition to primary. This behavior also negatively affects move_chunk_respects_maxtimems.js as seen in BF-24522. As a result, it's possible for moveChunk and/or the verification step to fail due to being unable to satisfy the read preference:
[js_test:move_chunk_respects_maxtimems] c21772| 2022-03-03T00:56:21.438+00:00 I REPL 21358 [conn63] "Replica set state transition","attr":{"newState":"SECONDARY","oldState":"PRIMARY"}
[js_test:move_chunk_respects_maxtimems] c21774| 2022-03-03T00:56:26.864+00:00 I REPL 21358 [ReplCoord-9] "Replica set state transition","attr":{"newState":"PRIMARY","oldState":"SECONDARY"}
[js_test:move_chunk_respects_maxtimems] s21775| 2022-03-03T00:56:36.524+00:00 D1 SHARDING 22772 [conn11] "Exception thrown while processing command","attr":{"db":"config","headerId":710,"error":"FailedToSatisfyReadPreference: Encountered non-retryable error during query :: caused by :: Could not find host matching read preference { mode: \"primary\" } for set move_chunk_respects_maxtimems-configRS"}
[js_test:move_chunk_respects_maxtimems] d21770| 2022-03-03T00:56:52.032+00:00 W SHARDING 23777 [MoveChunk] "Error while doing moveChunk","attr":{"error":"FailedToSatisfyReadPreference: Could not find host matching read preference { mode: \"primary\" } for set move_chunk_respects_maxtimems-configRS"}
[js_test:move_chunk_respects_maxtimems] c21774| 2022-03-03T00:56:52.057+00:00 I REPL 21331 [OplogApplier-0] "Transition to primary complete; database writes are now permitted"
Lacking a workaround, move_chunk_respects_maxtimems.js should be removed from the sharding_csrs_continuous_config_stepdown suite.
- is related to
-
SERVER-59891 Replace the coverage from sharding_continuous_config_stepdown.yml and then delete the test suite
-
- Backlog
-