[ 
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 
auto-deprioritized-minor  (was: Connector ElasticSearch 
auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Minor, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> 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: Not a Priority
>              Labels: Connector, ElasticSearch, auto-deprioritized-major, 
> auto-deprioritized-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.20.1#820001)

Reply via email to