[SERVER-71006] Small window of inconsistency for reads after turning index to multikey Created: 01/Nov/22  Updated: 29/Oct/23  Resolved: 08/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.15, 6.0.4, 6.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Henrik Edin Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.1, v6.0, v5.0
Sprint: Execution Team 2022-11-14
Participants:

 Description   

When turning an index into multikey we flip the in-memory state in an onCommit handler. This means there is a window between the WT transaction committing and updating the in-memory state where a reader can observe the data but not seeing the index as multi-key.



 Comments   
Comment by Githook User [ 09/Jan/23 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-71006 Fix race where a reader does not observe a concurrent multikey write

(cherry picked from commit cf648f7bc75f11fa316f6e9fbb737cf9763742c3)
Branch: v6.0
https://github.com/mongodb/mongo/commit/5d4498a56e4ffdef626e1bf855b8626988ecaebe

Comment by Githook User [ 09/Jan/23 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-71006 Fix race where a reader does not observe a concurrent multikey write

(cherry picked from commit cf648f7bc75f11fa316f6e9fbb737cf9763742c3)
Branch: v5.0
https://github.com/mongodb/mongo/commit/d7f52aa145180f3b86acd91223a2a3c4abfbff2b

Comment by Githook User [ 08/Nov/22 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-71006 Fix race where a reader does not observe a concurrent multikey write
Branch: master
https://github.com/mongodb/mongo/commit/cf648f7bc75f11fa316f6e9fbb737cf9763742c3

Generated at Thu Feb 08 06:17:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.