[SERVER-68908] Index builds in standalone mode should write out the _wt_table_checks file Created: 17/Aug/22  Updated: 05/Dec/22  Resolved: 23/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.4.16, 4.2.22
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-68925 Reintroduce check table logging setti... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:
Case:

 Description   

Rolling index builds are not compatible with the optimization introduced in SERVER-43664. Index builds in standalone mode should write out the _wt_table_checks file to the dbpath. This causes startup recovery to modify the table log settings for all tables.

The alternative is to revert SERVER-43664.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 23/Aug/22 ]

Doesn't work with cloud processes. Closing.

Comment by Josef Ahmad [ 18/Aug/22 ]

I've filed SERVER-68925 to revert SERVER-43664. Note that SERVER-68925 would be a more comprehensive alternative to SERVER-68908 because it'll address pre-existing inconsistencies as well.

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