[SERVER-36005] `IndexCatalogEntryImpl::_catalogIsReady` is unsafe to unconditionally call. Created: 07/Jul/18  Updated: 29/Oct/23  Resolved: 27/Jul/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.0.2, 4.1.2

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

Issue Links:
Backports
Depends
Related
is related to SERVER-35789 check for index catalog isready misma... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Storage NYC 2018-07-30
Participants:
Linked BF Score: 19

 Description   

The condition added here is to guard against WT snapshot isolation with read timestamp semantics where a read timestamp of T can sometimes not see committed updates [index build completions] at time < T if the WT transaction were opened before the update [index build] was committed.

However, while it's possible the timing of events would show storage seeing an index as building, but not complete, it's also possible the storage engine doesn't see the index build having begun. In that circumstance, a call to `_catalogIsReady` is fatal.



 Comments   
Comment by Githook User [ 20/Aug/18 ]

Author:

{'name': 'Dewal Gupta', 'email': 'dewal.gupta@10gen.com', 'username': 'dewalg'}

Message: SERVER-36005 Prevent unsafe IndexCatalogEntryImpl::_catalogIsReady call

(cherry picked from commit dfdffb7e4588d41c99e625ade8e9aa638b0c3fd4)
Branch: v4.0
https://github.com/mongodb/mongo/commit/5b5502a6947d12356b1fd3e44ad07e4f2453be41

Comment by Githook User [ 27/Jul/18 ]

Author:

{'name': 'Dewal Gupta', 'email': 'dewal.gupta@10gen.com', 'username': 'dewalg'}

Message: SERVER-36005 Prevent unsafe IndexCatalogEntryImpl::_catalogIsReady call
Branch: master
https://github.com/mongodb/mongo/commit/dfdffb7e4588d41c99e625ade8e9aa638b0c3fd4

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