fix(storagenode): handle unexpected LLSN errors #1005
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1005 +/- ##
==========================================
- Coverage 79.74% 79.53% -0.21%
==========================================
Files 178 178
Lines 21478 21531 +53
==========================================
- Hits 17127 17125 -2
- Misses 3562 3608 +46
- Partials 789 798 +9 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
hungryjang
approved these changes
Mar 6, 2025
…e metrics This commit enables Varlog to support both new and deprecated OpenTelemetry runtime metrics. Previously, Varlog only supported the deprecated runtime instrumentation. This change ensures backward compatibility by simultaneously setting the `OTEL_GO_X_DEPRECATED_RUNTIME_METRICS` environment variable and using the new version. This enhancement allows Varlog to leverage the latest OpenTelemetry features while maintaining compatibility with older versions, collecting more comprehensive runtime metrics.
Add validation for empty payloads in the Append RPC. If there is no payload in the append request, the RPC returns a gRPC status code of InvalidArgument.
This PR adds a new flag `--enable-development-mode` to enable development mode for the logger. If it is true, the logger panics at the DPanic level.
This PR adds error handling to prevent panic when an unexpected LLSN is encountered in backup and primary replicas. If `--enable-development-mode` is set, panic occurs as before.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does
This PR adds error handling to prevent panic when an unexpected LLSN is
encountered in backup and primary replicas. If
--enable-development-modeisset, panic occurs as before.