ethdb/pebble: fix pebble metrics registration #29699
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
|
Sorry, what's the issue fixed by this pull request? As you said, |
fjl
approved these changes
May 6, 2024
|
jorgemmsilva
pushed a commit
to iotaledger/go-ethereum
that referenced
this pull request
Jun 17, 2024
ethdb/pebble: use GetOrRegister instead of NewRegistered when creating metrics
stwiname
pushed a commit
to subquery/data-node-go-ethereum
that referenced
this pull request
Sep 9, 2024
ethdb/pebble: use GetOrRegister instead of NewRegistered when creating metrics
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.
Pebble gauge metrics are stuck when opening a database for the second time (within the same metrics namespace, after closing first one).
Gauge metrics are created with
metrics.NewRegisteredGaugeand it fails silently if metric name already exists. The Meter metrics work despite thatmetrics.NewRegisteredMeteris used, because it callsmetrics.GetOrRegisterMeterinternally.This PR fixes the issue by using
metrics.GetOrRegister*functions instead.