You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2022/08/09 08:35:00 UTC

[jira] [Closed] (FLINK-28785) Hybrid shuffle consumer thread and upstream thread may have dead lock

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

Xintong Song closed FLINK-28785.
--------------------------------
    Resolution: Fixed

master (1.16): b442394c65b1e924c4b5710a9453e3c7eacf05b5

> Hybrid shuffle consumer thread and upstream thread may have dead lock 
> ----------------------------------------------------------------------
>
>                 Key: FLINK-28785
>                 URL: https://issues.apache.org/jira/browse/FLINK-28785
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Network
>    Affects Versions: 1.16.0
>            Reporter: Weijie Guo
>            Assignee: Weijie Guo
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.16.0
>
>
> In hybrid shuffle mode, subpartition view lock will be acquired by consumer thread, and further wait the read lock of MemoryDataManager. But MemoryDataManager may acquire write lock to make a global spilling decision, and then wait subpartition view lock to get consuming offset. In this case, deadlock will occurs.
> consumer thread : acqurie subpartition lock -> wait read lock.
> upstream thread  : acquire write lock -> wait subpartition lock.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)