-
Notifications
You must be signed in to change notification settings - Fork 199
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
[Bug]: SPU fails with "not enough for records" #2509
Labels
bug
Something isn't working
no-stale
Opt-out of closing issue due to no activity
SPU
SPU related
Stability/Scalability
Milestone
Comments
@galibey Can you look into this? |
Stale issue message |
bors bot
pushed a commit
that referenced
this issue
Dec 28, 2022
changes related to issue #2509 - Updated Storage CLI to validate log entries - Use anyhow in the storage validation to simplify error handling. - Internal refactoring of API to simplify validation handling such as `next` -> `try_next`
bors bot
pushed a commit
that referenced
this issue
Dec 30, 2022
resolves #2509. Recover from invalid logs due to incorrect batch encoding. It does this by setting the log size to the last correct batches. Tested with data from corrupted segments. - More clean and simplification of the Log validator. - Migrated more API to use anyhow
bors bot
pushed a commit
that referenced
this issue
Dec 30, 2022
resolves #2509. Recover from invalid logs due to incorrect batch encoding. It does this by setting the log size to the last correct batches. Tested with data from corrupted segments. - More clean and simplification of the Log validator. - Migrated more API to use anyhow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
no-stale
Opt-out of closing issue due to no activity
SPU
SPU related
Stability/Scalability
What happened
No response from SPU when producing
Describe the setup
How to reproduce it (as minimally and precisely as possible)
Not sure
Log output
SPU:
The text was updated successfully, but these errors were encountered: