[SERVER-16959] Collection::updateDocument() issues an INVALIDATION_MUTATION after performing an in-place update (MMAP v1) Created: 20/Jan/15  Updated: 05/Feb/15  Resolved: 22/Jan/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.0.0-rc6

Type: Bug Priority: Critical - P2
Reporter: David Storch Assignee: David Storch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
tested by SERVER-17192 Add regression tests for timing of in... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

In 2.6, the invalidation occurs before performing an in-place document update:

https://github.com/mongodb/mongo/blob/r2.6.7/src/mongo/db/catalog/collection.cpp#L384-L391

Due to a refactor to permit a pluggable storage API, mutation invalidations for in-place document updates now occur after the write. The intention of the validation framework is to notify active queries of writes that are about to happen, not ones that have already occurred.

Affects only version 2.8 mongod configured with the MMAP v1 storage engine.



 Comments   
Comment by Githook User [ 22/Jan/15 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-16959 send INVALIDATION_MUTATION message prior to an in-place update
Branch: master
https://github.com/mongodb/mongo/commit/34f4776efba9205b9969232bce905f681ac8bac3

Generated at Thu Feb 08 03:42:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.