[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: |
|
||||||||||||||||
| 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: (cherry picked from commit dfdffb7e4588d41c99e625ade8e9aa638b0c3fd4) |
| Comment by Githook User [ 27/Jul/18 ] |
|
Author: {'name': 'Dewal Gupta', 'email': 'dewal.gupta@10gen.com', 'username': 'dewalg'}Message: |