-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add broken index backup #2034
add broken index backup #2034
Conversation
Deploying with Cloudflare Pages
|
[CHATOPS:HELP] ChatOps commands.
|
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #2034 +/- ##
==========================================
+ Coverage 29.50% 29.99% +0.48%
==========================================
Files 366 366
Lines 34664 34797 +133
==========================================
+ Hits 10228 10437 +209
+ Misses 24000 23879 -121
- Partials 436 481 +45
☔ View full report in Codecov by Sentry. |
af53c44
to
e6e014b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Profile Report
|
Profile Report
|
Description:
The current behavior when loading broken indexes is to discard all of them and continue running with a clean state (remove continuous). This makes it impossible to investigate broken indexes later. To address this, this PR adds a feature to allow the configuration of the number of broken indexes to be saved, enabling the investigation of broken indexes later.
This PR also changes the path to store indexes when CoW is disabled, from
n.path
ton.path/origin
to match with the path that's used when CoW is enabled.ngt.rebuild
to migrate for the backup processmigrate
function to do the migrationTestNew
covers everything)agent.ngt.broken_index_history_limit
parameterinternal/test/data/agent/ngt/validIndex/*
as a test index dataagent
stand alone in the devcontainerRelated Issue:
Versions:
Checklist:
Special notes for your reviewer: