Operational Defect Database

BugZero found this defect 2530 days ago.

MongoDB | 367634

[SERVER-28490] Check the state after acquiring the lock in bgsync

Last update date:

12/6/2017

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.4.5

3.5.7

Description:

Info

In bgsync, due to shutdown, we need to check the state after locking whenever it's going to change any state that the destruct won't clean up. This includes the construction of _syncSourceResolver, _oplogFetcher and _rollback.

Top User Comments

xgen-internal-githook commented on Wed, 3 May 2017 00:11:26 +0000: Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'} Message: SERVER-28490 Check the state after acquiring the lock in bgsync. (cherry picked from commit b077e090642dbb50ea235e2b26af90399896eb04) Branch: v3.4 https://github.com/mongodb/mongo/commit/f55883b2c7e530a669e9c93ae3a41654ab4dae4f xgen-internal-githook commented on Sat, 22 Apr 2017 03:05:35 +0000: Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'} Message: SERVER-28490 Check the state after acquiring the lock in bgsync. Branch: master https://github.com/mongodb/mongo/commit/b077e090642dbb50ea235e2b26af90399896eb04

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:

...