Skip to content
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

[otlp grpc] Handle retry in case of DEADLINE_EXCEEDED response code #5436

Open
vishweshbankwar opened this issue Mar 11, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@vishweshbankwar
Copy link
Member

Spec suggests that DEADLINE_EXCEEDED is a retryable status code.

The current retry logic for otlp exporters would not retry any errors that would extend the export duration beyond the configured timeout period. This timeout is used as the deadline for a single grpc request that is sent to the server by the export client. In other words, the timeout period would be exhauted by a single grpc request and the request would not be retried (Not following the spec).

Opening this issue to further investigate how to handle DEADLINE_EXCEEDED response code in grpc.

@vishweshbankwar vishweshbankwar added the bug Something isn't working label Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant