Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
About this change - What it does:
S3 client metrics (JMX bean
aiven.kafka.server.tieredstorage.s3:type=s3-client-metrics) stay at zero for operations different than GetObject, all other operation like PutObject, DeleteObjects, etc.This change keeps a single shared
Metricsand sensor map per JVM (via a staticSharedMetricsholder). AllMetricCollectorinstances record into that shared state, so the single JMX bean always reflects all S3 API calls.close()is a no-op so one collector’s shutdown does not unregister the shared metrics.bean attribute's data for broker with storage-s3.jar built with this change
bean attribute's data for broker with storage-s3-1.1.1.jar
Resolves: #802
Why this way