-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
Track RequestedRangeNotSatisfiedException separately in S3 Metrics #109657
Conversation
Due to RCO changes, we started getting a lot of `RequestedRangeNotSatisfiedException`s which are expected. We would like to not count them as failures and track them separately.
Hi @arteam, I've created a changelog YAML for you. |
Pinging @elastic/es-distributed (Team:Distributed) |
...nalClusterTest/java/org/elasticsearch/repositories/s3/S3BlobStoreRepositoryMetricsTests.java
Show resolved
Hide resolved
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.
Thanks for working on this. I left a question.
server/src/main/java/org/elasticsearch/repositories/RepositoriesMetrics.java
Show resolved
Hide resolved
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.
Nice. Some questions/comments.
server/src/main/java/org/elasticsearch/repositories/RepositoriesMetrics.java
Outdated
Show resolved
Hide resolved
modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3BlobStore.java
Outdated
Show resolved
Hide resolved
modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3BlobStore.java
Outdated
Show resolved
Hide resolved
…esMetrics.java Co-authored-by: Iraklis Psaroudakis <[email protected]>
…-not-satisfied-exceptions
modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3BlobStore.java
Show resolved
Hide resolved
...nalClusterTest/java/org/elasticsearch/repositories/s3/S3BlobStoreRepositoryMetricsTests.java
Outdated
Show resolved
Hide resolved
modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3BlobStore.java
Outdated
Show resolved
Hide resolved
modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3BlobStore.java
Show resolved
Hide resolved
@elasticmachine update branch |
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. However, I'd suggest to get one more approval, ideally @ywangd 's, before merging.
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
I have some minor comments for your consideration. Thanks!
modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3BlobStore.java
Outdated
Show resolved
Hide resolved
modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3BlobStore.java
Outdated
Show resolved
Hide resolved
It's not useful since request range requests are not retryable and we should have mostly one error
@elasticmachine update branch |
@elasticmachine update branch |
Due to RCO changes, we started getting a lot of
RequestedRangeNotSatisfiedException
s which are expected. We would like track them separately.This change a new metrics
es.repositories.exceptions.request_range_not_satisfied.total
to track all client errors analogous to other S3 errors.In the future, we can add the error code as an attribute to the metrics, so we can adapt it to all client errors.