-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Conventionally use RejectedExecutionException for load issues #2511
Conventionally use RejectedExecutionException for load issues #2511
Conversation
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.
there might be a mockwebserver test for the span consumer. it could be helpful to use a real response and show that it works
I found the ElasticsearchSpanConsumerTest and the MockWebServer it uses. However, I didn't notice any tests for span indexing to base things off of. So I wrote a more direct HttpBulkIndexerTest to validate this behavior. Does that work? |
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.
looks good to me.
we can merge on green. as this is a minor change I suspect it isnt blocking on iCLA such as the major refactoring change is.. |
...-storage/elasticsearch/src/test/java/zipkin2/elasticsearch/internal/HttpBulkIndexerTest.java
Show resolved
Hide resolved
…sts" error and throw more descriptive exception.
60bf284
to
b1e119c
Compare
thanks. let me know if you want a hand rebasing your other branch/PR |
Updating Elasticsearch's HttpBulkIndexer to check for "too many requsts" error and throw more descriptive exception.