-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/elasticsearch] Data should not be dropped with persistent queue enabled when ES cluster is temporarily unavailable #30792
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hello @ycombinator, can you share collector logs during this process, preferably with logging set to |
Hi @crobert-1, here are the collector logs over the course of all the steps, at debug level:
|
The sending queue doesn't retry when the upload fails. To enable retry_on_failure , 2 changes are required:
The second step will be a little tricky to implement since the bulk indexer delays uploading data until the buffer is full. So, the exporter cannot immediately know if the upload fails. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I'm working on a few PRs to improve the reliability of Elasticsearch exporter in cases like ES downtime and collector crashes. The plan is that #32377 resolves this very issue. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
#32377 is still WIP. |
Component(s)
exporter/elasticsearch
What happened?
Description
If the Elasticsearch exporter is configured with a persistent queue (
sending_queue.storage: filestorage
) and new data is written to this persistent queue while the Elasticsearch cluster is temporarily unavailable, this data should be indexed into Elasticsearch once the cluster becomes available again.Steps to Reproduce
Expected Result
Actual Result
Collector version
v0.93.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") MacOS
Compiler(if manually compiled): (e.g., "go 14.2") go 1.21.6
OpenTelemetry Collector configuration
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: