[feat](fe) add recovery_journal_id to truncate bdbje logs#60738
[feat](fe) add recovery_journal_id to truncate bdbje logs#60738gavinchou merged 4 commits intoapache:masterfrom
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 28982 ms |
TPC-DS: Total hot run time: 185005 ms |
FE UT Coverage ReportIncrement line coverage |
|
run buildall |
|
run buildall |
TPC-H: Total hot run time: 29060 ms |
TPC-DS: Total hot run time: 184443 ms |
FE UT Coverage ReportIncrement line coverage |
FE Regression Coverage ReportIncrement line coverage |
|
run buildall |
6c5eb0a to
c1124cc
Compare
FE UT Coverage ReportIncrement line coverage |
|
run buildall |
TPC-H: Total hot run time: 28793 ms |
TPC-DS: Total hot run time: 184012 ms |
FE UT Coverage ReportIncrement line coverage |
|
run buildall |
FE UT Coverage ReportIncrement line coverage |
TPC-H: Total hot run time: 28712 ms |
TPC-DS: Total hot run time: 183217 ms |
|
PR approved by at least one committer and no changes requested. |
It only works for metadata_failure_recovery mode
Problem Summary:
When using metadata failure recovery mode, sometimes the journal logs need to be truncated to a specific journal ID to recover from metadata corruption. This PR adds a new parameter
--recovery_journal_idto allow users to specify the target journal ID, and all journals with IDs greater than this value will be removed.How to use
When the Frontend (FE) metadata is corrupted and needs to be recovered, follow these steps:
--metadata_failure_recoveryand--recovery_journal_idparameters:For example, to recover to journal ID 12345:
Note: This operation will permanently delete metadata journals. Make sure to backup your data before using this feature.