Operational Defect Database

BugZero found this defect 2631 days ago.

MongoDB | 338436

[SERVER-27397] Disable OplogFetcher sync source re-evaluation during initial sync

Last update date:

4/5/2017

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.4.2

3.5.2

Description:

Info

The OplogFetcher will terminate with an error if it decides that another sync source would be better than its current one. This causes initial sync to fail. Since initial sync does not allow for sync source changes, it should not check if there are better sync sources. If there is a problem on the sync source, it will manifest itself in the cloning phase as well, and cause a failure there.

Top User Comments

xgen-internal-githook commented on Sun, 22 Jan 2017 03:35:07 +0000: Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'} Message: SERVER-27397 disable OplogFetcher sync source re-evaluation during initial sync (cherry picked from commit 4b35e713718e1d0f44dae516726b173c150efcef) Branch: v3.4 https://github.com/mongodb/mongo/commit/68eb7dad8c49e9d379860452e7ee583a393435d8 xgen-internal-githook commented on Wed, 18 Jan 2017 16:26:38 +0000: Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'} Message: SERVER-27397 disable OplogFetcher sync source re-evaluation during initial sync Branch: master https://github.com/mongodb/mongo/commit/4b35e713718e1d0f44dae516726b173c150efcef

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:

...