[SERVER-32028] Make reconfig() in rslib.js resilient to NodeNotFound error Created: 17/Nov/17  Updated: 30/Oct/23  Resolved: 28/Nov/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.3, 3.7.1

Type: Bug Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Siyuan Zhou
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-49305 Remove reconfig retries in our tests Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: Repl 2017-12-04
Participants:
Linked BF Score: 0

 Description   

If the connections used for heartbeats get closed on the node, reconfig command will return an error like the following. reconfig() is only used for testing and should be resilient to this error.

{
  "ok" : 0,
  "errmsg" : "Quorum check failed because not enough voting nodes responded; required 2 but only the following 1 voting nodes responded: ip-10-187-92-235:21010; the following nodes did not respond affirmatively: ip-10-187-92-235:21011 failed with End of file, ip-10-187-92-235:21012 failed with End of file",
  "code" : 74,
  "codeName" : "NodeNotFound",
  ...
}



 Comments   
Comment by Githook User [ 12/Jan/18 ]

Author:

{'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou', 'username': 'visualzhou'}

Message: SERVER-32028 Make reconfig() in rslib.js resilient to NodeNotFound error

(cherry picked from commit 672cc4c67de8cba44901cf6db1cc346016848a35)
Branch: v3.6
https://github.com/mongodb/mongo/commit/25f1ad63b3f24e56df51d811e7722a1cb2dd7433

Comment by Githook User [ 28/Nov/17 ]

Author:

{'name': 'Siyuan Zhou', 'username': 'visualzhou', 'email': 'siyuan.zhou@mongodb.com'}

Message: SERVER-32028 Make reconfig() in rslib.js resilient to NodeNotFound error
Branch: master
https://github.com/mongodb/mongo/commit/672cc4c67de8cba44901cf6db1cc346016848a35

Generated at Thu Feb 08 04:28:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.