[SERVER-24004] move serverStatus() into try...catch in reconfig_without_increased_queues.js Created: 02/May/16  Updated: 18/Nov/16  Resolved: 02/May/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.2.7, 3.3.6

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Done Votes: 0
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl 14 (05/13/16)
Participants:
Linked BF Score: 0

 Description   

serverStatus can fail if a primary steps down during a reconfig. It should be moved into the try...catch so a failure leads to a retry.



 Comments   
Comment by Githook User [ 16/May/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-24004 move serverStatus() into try block in reconfig_without_increased_queues.js

(cherry picked from commit 76a5e948d538c1afcce38ad8377d55765b8e63c0)
Branch: v3.2
https://github.com/mongodb/mongo/commit/0e99416408f62276245216949b7eb93259ec1d5c

Comment by Dianna Hohensee (Inactive) [ 16/May/16 ]

The error this fixes (BF-2329) is appearing in the 3.2 branch: https://evergreen.mongodb.com/task/mongodb_mongo_v3.2_enterprise_rhel_71_ppc64le_replicasets_legacy_a0b042b01f7ec2e3b086f189e5695785092d1657_16_05_10_17_11_45. If you could backport the fix, that would be perfect.

Comment by Githook User [ 02/May/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-24004 move serverStatus() into try block in reconfig_without_increased_queues.js
Branch: master
https://github.com/mongodb/mongo/commit/76a5e948d538c1afcce38ad8377d55765b8e63c0

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