flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weihua Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8020) Deadlock found in Flink Streaming job
Date Wed, 08 Nov 2017 08:47:00 GMT

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

Weihua Jiang commented on FLINK-8020:
-------------------------------------

Sorry, after further analyzing, it seems the deadlock is caused by the mixing of our lock
with flink lock. After reorganizing our code, the deadlock can be eliminated. 

> Deadlock found in Flink Streaming job
> -------------------------------------
>
>                 Key: FLINK-8020
>                 URL: https://issues.apache.org/jira/browse/FLINK-8020
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector, Streaming, Streaming Connectors
>    Affects Versions: 1.3.2
>         Environment: Kafka 0.8.2 and Flink 1.3.2 on YARN mode
>            Reporter: Weihua Jiang
>            Priority: Blocker
>         Attachments: jstack67976-2.log
>
>
> Our streaming job run into trouble in these days after a long time smooth running. One
issue we found is [https://issues.apache.org/jira/browse/FLINK-8019] and another one is this
one.
> After analyzing the jstack, we believe  we found a DEAD LOCK in flink:
> 1. The thread "cache-process0 -> async-operator0 -> Sink: hbase-sink0 (8/8)" hold
lock 0x00000007b6aa1788 and is waiting for lock 0x00000007b6aa1940.
> 2. The thread "Time Trigger for cache-process0 -> async-operator0 -> Sink: hbase-sink0
(8/8)" hold lock 0x00000007b6aa1940 and is waiting for lock 0x00000007b6aa1788. 
> This DEADLOCK made the job fail to proceed. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message