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

Posted to issues@flink.apache.org by "Thomas Weise (Jira)" <ji...@apache.org> on 2019/09/17 20:56:00 UTC

[jira] [Updated] (FLINK-14107) Kinesis consumer record emitter deadlock under event time alignment

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

Thomas Weise updated FLINK-14107:
---------------------------------
    Summary: Kinesis consumer record emitter deadlock under event time alignment  (was: Kinesis consumer record emitter may deadlock under event time alignment)

> Kinesis consumer record emitter deadlock under event time alignment
> -------------------------------------------------------------------
>
>                 Key: FLINK-14107
>                 URL: https://issues.apache.org/jira/browse/FLINK-14107
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kinesis
>    Affects Versions: 1.8.2, 1.9.0
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When the emitter reaches the max timestamp for the current queue, it stops emitting and waits for the max timestamp to advance. Since it simultaneously selects the next queue as the new "minimum" queue, it may deadlock if the previous min queue represents the new global lower bound after the max timestamp advanced. This occurs very infrequently and we were finally able to reproduce.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)