[SERVER-26139] Need to abandon snapshot after replication spawns a background index build Created: 16/Sep/16  Updated: 02/Feb/17  Resolved: 21/Sep/16

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Replication
Affects Version/s: None
Fix Version/s: 3.2.13, 3.4.0-rc0

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.2
Sprint: Integration 2016-10-10
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 02/Feb/17 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-26139 Abandon snapshot after spawning a background index build

Also adds extra logging to help debug similar future issues.

(cherry picked from commit c66a623167c156f953781949deef68b07ee1b9f0)
Branch: v3.2
https://github.com/mongodb/mongo/commit/94efd182f3bdcf1eafe7317b94b315d9551517fe

Comment by Githook User [ 21/Sep/16 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-26139 Abandon snapshot after spawning a background index build

Also adds extra logging to help debug similar future issues.
Branch: master
https://github.com/mongodb/mongo/commit/c66a623167c156f953781949deef68b07ee1b9f0

Comment by Eric Milkie [ 16/Sep/16 ]

Because the applyops code drops its database lock to spawn the background index build thread, we must treat this the same as when a normal user operation yields – we must refresh our snapshot in case metadata has changed while the lock was dropped. Otherwise, our metadata cache may be out of sync with what is actually in the storage engine.

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