You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The root cause of the panic is the handling of bulk failures (ref). When the item fails then we try to push the item back into the bulk indexer, however, if the exporter is shutting down then the bulkindexer would already be closed and the flush (which led to the error) is due to ES not available on the final flush initiated by Close.
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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Component(s)
exporter/elasticsearch
What happened?
Description
If Elasticsearch is unavailable on shutdown of the exporter then if there is data to be flushed in the exporter it will cause a panic.
Steps to Reproduce
Expected Result
No panic is observed
Actual Result
Panic is observed:
The root cause of the panic is the handling of bulk failures (ref). When the item fails then we try to push the item back into the bulk indexer, however, if the exporter is shutting down then the bulkindexer would already be closed and the flush (which led to the error) is due to ES not available on the final flush initiated by
Close
.Collector version
all
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
panic: send on closed channel goroutine 78 [running]: github.com/elastic/go-elasticsearch/v7/esutil.(*bulkIndexer).Add(0x14000334a80, {0x102586420, 0x1033c5460}, {{0x101f86420, 0x14}, {0x101f70693, 0x6}, {0x0, 0x0}, {0x0, ...}, ...})
Additional context
No response
The text was updated successfully, but these errors were encountered: