fix(core): make WAL apply lag metrics persistent across restarts#6017
fix(core): make WAL apply lag metrics persistent across restarts#6017bluestreak01 merged 11 commits intomasterfrom
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
27cff28 to
6de29b2
Compare
|
@coderabbitai review please |
🧩 Analysis chainI'll review the changes for making WAL apply lag metrics persistent across restarts. Let me examine the code changes first. 🏁 Script executed: Length of output: 779 Let me explore the repository structure to find the correct file paths and examine the changes. 🏁 Script executed: Length of output: 11941 Now let me examine the actual files and get the recent changes: 🏁 Script executed: Length of output: 279773 Let me examine the specific changes made in this PR: 🏁 Script executed: Length of output: 303250 @ideoma: The changes ensure WAL apply lag metrics are now tracked and updated persistently across restarts, using the metrics infrastructure in a systematic way. The implementation is clean, aligns with the PR objective, and is well-covered by tests. No issues found—approved. ✅ Actions performedComments resolved. |
[PR Coverage check]😍 pass : 17 / 19 (89.47%) file detail
|
PR questdb/questdb#6017 changes these names, this is a followup.
Fixes #6001.