[ 
https://issues.apache.org/jira/browse/FLINK-21511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-21511:
-----------------------------------
    Labels: auto-unassigned pull-request-available stale-major  (was: 
auto-unassigned pull-request-available)

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 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> 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: Major
>              Labels: auto-unassigned, pull-request-available, stale-major
>
> 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.3.4#803005)

Reply via email to