Operational Defect Database

BugZero found this defect 2537 days ago.

MongoDB | 365848

[SERVER-28387] Extend secondary catchup period during stepdown in server-23299-1.js

Last update date:

12/6/2017

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.4.5

Description:

Info

In server-23299-1.js, there is at least one place where a primary is stepped down with a default secondaryCatchupPeriodSecs (https://github.com/mongodb/mongo/blob/ee0ff4acca5ac5704eb2208d3b58839c5ce0eb80/jstests/multiVersion/server-23299-1.js#L87). We should extend this to at least 60 seconds to allow for potentially slow nodes/machines that might still be catching up. Note that this test was deleted on 3.5 by commit https://github.com/mongodb/mongo/commit/eda82cb72e0271604267a9d80f5468d5b0dbc348

Top User Comments

xgen-internal-githook commented on Fri, 21 Apr 2017 20:36:48 +0000: Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'} Message: SERVER-28387 Extend secondary catchup period during stepdown in server-23299-1.js Branch: v3.4 https://github.com/mongodb/mongo/commit/70415a0fc5019a61954c62c52936f3961cb8c47e

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...