[
https://issues.apache.org/jira/browse/FLINK-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-18535:
-----------------------------------
Labels: Connector ElasticSearch auto-deprioritized-major stale-minor (was:
Connector ElasticSearch auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Elasticsearch connector hangs for threads deadlocked
> -----------------------------------------------------
>
> Key: FLINK-18535
> URL: https://issues.apache.org/jira/browse/FLINK-18535
> Project: Flink
> Issue Type: Bug
> Components: Connectors / ElasticSearch
> Affects Versions: 1.10.0
> Reporter: DeFOX
> Priority: Minor
> Labels: Connector, ElasticSearch, auto-deprioritized-major,
> stale-minor
>
> When using the connector created by
> org.apache.flink.streaming.connectors.elasticsearch7.ElasticsearchSink.Builder
> to sink data to ES(es7.7.1 and es6.8.5), flink job will finally hang for
> threads deadlocked after a while.
> And connector created by
> org.apache.flink.streaming.connectors.elasticsearch6.ElasticsearchSink.Builder
> will not result in this deadlocked situation.
> This deadlocked issue may come from this
> pr：[https://github.com/elastic/elasticsearch/pull/41451]
> So upgrade version of the dependencies of ES may fix this bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
