You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Fabian Paul (Jira)" <ji...@apache.org> on 2022/01/03 12:08:00 UTC

[jira] [Commented] (FLINK-21511) Flink connector elasticsearch 6.x has a bug about BulkProcessor hangs for threads deadlocked

    [ https://issues.apache.org/jira/browse/FLINK-21511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467947#comment-17467947 ] 

Fabian Paul commented on FLINK-21511:
-------------------------------------

Fixed as part of https://issues.apache.org/jira/browse/FLINK-24323

> Flink connector elasticsearch 6.x has a  bug about BulkProcessor hangs for threads deadlocked
> ---------------------------------------------------------------------------------------------
>
>                 Key: FLINK-21511
>                 URL: https://issues.apache.org/jira/browse/FLINK-21511
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / ElasticSearch
>    Affects Versions: 1.10.3, 1.11.3, 1.12.1
>            Reporter: zhangmeng
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned, pull-request-available
>
> We use flink1.10, flink elasticsearch connector 6.x to write elasticsearch. A total of 50 tasks running a weeks. There were more than 30 tasks that no longer wrote data. Investigation found that there was a deadlock bug in the current version of elasticsearch. and fixed on high version.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)