[SERVER-64234] Remove move_chunk_respects_maxtimems.js from sharding_csrs_continuous_config_stepdown suite Created: 04/Mar/22  Updated: 29/Oct/23  Resolved: 26/May/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Brett Nawrocki Assignee: Nandini Bhartiya
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-59891 Replace the coverage from sharding_co... Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding NYC 2022-05-16, Sharding NYC 2022-05-30
Participants:
Linked BF Score: 0
Story Points: 1

 Description   

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.



 Comments   
Comment by Githook User [ 23/May/22 ]

Author:

{'name': 'nandinibhartiyaMDB', 'email': 'nandini.bhartiya@mongodb.com', 'username': 'nandinibhartiyaMDB'}

Message: SERVER-64234: Exclude move_chunk_respects_maxtimems.js
Branch: master
https://github.com/mongodb/mongo/commit/40ee0b78381bf5c4585ddd2c9fb513129205d22c

Generated at Thu Feb 08 05:59:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.