retry_on_failure for jaeger_storage_exporter #7105
-
|
Hello folks, I am working on deploying Jaeger V2 with OpenTelemetry CRD. The storage backend is Elasticsearch. I have deployed it in my local cluster, and it is working fine. Though I am struggling with one issue. I want to tune the queue size and retry mechanism for exporter failures. I found that we can set the queue size using Now, the general [exporterhelper](https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/exporterhelper/README.md#:~:text=can%20be%20modified%3A-,retry_on_failure,-enabled%20(default%20%3D%20true) provides a mechanism to But I am not able to find any documentation on Jaeger that shows how to leverage the same in the Jaeger v2 storage backend. Appreciate your help, and thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
|
Hello @aujjwal-smarsh! I'm Dosu, here to help you solve bugs, answer your questions, and guide you on your journey as a contributor. While you're waiting for a human maintainer, feel free to let me know how I can assist you! The Jaeger V2 storage backend does not support the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
Beta Was this translation helpful? Give feedback.
-
|
Hey @aujjwal-smarsh! I'm here to help with technical questions and bug-solving, but diving into the specifics of Jaeger's design decisions or involving individuals directly is a bit beyond my scope. If you think I should be able to assist with this, feel free to reach out to the Dosu Team. They'll be happy to hear your feedback! 😊 To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
Beta Was this translation helpful? Give feedback.
-
|
Historically jaeger-v1 storage implementations were expected to decide if they want to support retries, since depending on the storage implementation an export may not be idempotent. I think it's ok to allow this configuration in the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @yurishkuro for providing the details. Is there a plan currently in the pipeline on the above lines? I see a lot of good work happening for Jaeger v2, considering Jaeger v1 is getting EOL by this year's end. It would be awesome to have this support for backoff retries as well. |
Beta Was this translation helpful? Give feedback.
-
|
I opened an issue #7110 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @yurishkuro. This would be a great value addition to Jaeger V2. |
Beta Was this translation helpful? Give feedback.
Hello @aujjwal-smarsh! I'm Dosu, here to help you solve bugs, answer your questions, and guide you on your journey as a contributor. While you're waiting for a human maintainer, feel free to let me know how I can assist you!
The Jaeger V2 storage backend does not support the
retry_on_failureconfiguration for exporters. The code explicitly disables the retry mechanism withexporterhelper.WithRetry(configretry.BackOffConfig{Enabled: false})[1].To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other