Operational Defect Database

BugZero found this defect 2537 days ago.

MongoDB | 365743

[SERVER-28378] Extend secondary catch up period in priority_takeover_two_nodes_equal_priority.js

Last update date:

12/6/2017

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.2.15

3.4.6

3.5.8

Description:

Info

The step down command in priority_takeover_two_nodes_equal_priority.js uses a default secondaryCatchupPeriodSecs value. We should extend it to at least 60 seconds to account for slow secondary machines.

Top User Comments

xgen-internal-githook commented on Thu, 22 Jun 2017 22:07:47 +0000: Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'} Message: SERVER-28378 Extend secondary catch up period in priority_takeover_two_nodes_equal_priority.js (cherry picked from commit 344de09ffc51bbc7786269917ebd1b417b940a7a) Branch: v3.2 https://github.com/mongodb/mongo/commit/3221f3ffcaf29ed36ce59453637321bdbd2a1fed xgen-internal-githook commented on Thu, 22 Jun 2017 19:19:45 +0000: Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'} Message: SERVER-28378 Extend secondary catch up period in priority_takeover_two_nodes_equal_priority.js (cherry picked from commit 344de09ffc51bbc7786269917ebd1b417b940a7a) Branch: v3.4 https://github.com/mongodb/mongo/commit/147a9b4b1970510cb4fb28bd2a58576f46b75f76 william.schultz commented on Fri, 19 May 2017 19:29:23 +0000: The build failure linked to this ticket occurred on the 3.2 branch. xgen-internal-githook commented on Fri, 19 May 2017 19:24:36 +0000: Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'} Message: SERVER-28378 Extend secondary catch up period in priority_takeover_two_nodes_equal_priority.js Branch: master https://github.com/mongodb/mongo/commit/344de09ffc51bbc7786269917ebd1b417b940a7a mrigal commented on Fri, 7 Apr 2017 10:30:21 +0000: Makes sense! Also you or @benety.goh might have a second look at https://jira.mongodb.org/browse/SERVER-26216 I really have big doubts this is "intended behaviour"...

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:

...