[SERVER-33503] Timestamp non-bulk multikey index commits Created: 27/Feb/18  Updated: 29/Oct/23  Resolved: 01/Mar/18

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Replication
Affects Version/s: None
Fix Version/s: 3.7.3

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: rollback-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-33418 Have index build completion also comm... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-03-12
Participants:

 Description   

SERVER-33418 was an incomplete change. Non-bulk index builds perform multikey updates while the index is building, bypassing the timestamping mechanism for multikey.

This ticket reflects a need to accumulate the multikey information and postpone making the updates until the index is being successfully committed.



 Comments   
Comment by Githook User [ 01/Mar/18 ]

Author:

{'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb', 'username': 'dgottlieb'}

Message: SERVER-33503: Complete timestamping multikey updates for background index builds.
Branch: master
https://github.com/mongodb/mongo/commit/82d0934425e83acfcb9c3b65a4fc52994ae58351

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