-
Notifications
You must be signed in to change notification settings - Fork 227
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
[GRPC] Fix max span handling in client interceptor #1861
[GRPC] Fix max span handling in client interceptor #1861
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.
This looks perfect! I'll let @beniwohli take a look as well and we'll get this merged.
Looks like there's a test failure against 3.11 with the latest grpc. You can ignore the |
Thanks for the quick reply. I was able to fix the grpc test. |
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.
Awesome, nice fix!
@elasticmachine, run elasticsearch-ci/docs |
Do you already know when this will be included in a release? We are currently affected by it in our production environments and mitigated it to some degree by increasing the max spans per transaction to 1k. But some of our processes occasionally die due to this. |
I think we'll probably release early next week. |
What does this pull request do?
This change fixes a bug when the maximum amount of spans in a transaction is already reached.
I'm not quite sure about the test though. I was not able to create a functional gRPC test environment on my local machine.
Related issues
Closes #1832