[SERVER-83748] Update the WT downgrade string to reflect the correct release values. Created: 30/Nov/23 Updated: 02/Feb/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Sprint: | Execution Team 2024-02-05, Execution Team 2024-02-19 |
| Participants: |
| Description |
|
Currently, during a clean shutdown, we downgrade the WT version for data files to be backward compatible. However, the WiredTigerFileVersion::getDowngradeString() method appears to provide an incorrect result, returning a stale WT version value ("10.0.0") . I think we should update to
I'm uncertain about the implications of this issue but observed it while investigating another WT-related problem. |