[SERVER-59147] Investigate the feasibility of taking a checkpoint when WT_SESSION.alter returns EBUSY during startup recovery Created: 05/Aug/21 Updated: 06/Dec/22 Resolved: 12/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | 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: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
This is a follow-up server ticket from the conversations held in During startup recovery, if the table logging settings need to be changed, there's a chance for WT_SESSION.alter to return EBUSY even if that command is executed after the recovery (see |
| Comments |
| Comment by Connie Chen [ 12/Aug/21 ] |
|
Closing this as "Won't do" since Storage Engines will be tackling |