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

Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2020/05/18 04:59:00 UTC

[jira] [Closed] (FLINK-17766) Use checkpoint lock instead of fine-grained locking in Kafka AbstractFetcher

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

Aljoscha Krettek closed FLINK-17766.
------------------------------------
    Resolution: Fixed

master: 59714b9d6addb1dbf2171cab937a0e3fec52f2b1

> Use checkpoint lock instead of fine-grained locking in Kafka AbstractFetcher
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-17766
>                 URL: https://issues.apache.org/jira/browse/FLINK-17766
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Connectors / Kafka
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Major
>             Fix For: 1.11.0
>
>
> In {{emitRecordsWithTimestamps()}}, we are currently locking on the partition state object itself to prevent concurrent access (and to make sure that changes are visible across threads). However, after recent changes (FLINK-17307) we hold the checkpoint lock for emitting the whole "bundle" of records from Kafka. We can now also just use the checkpoint lock in the periodic emitter callback and then don't need the fine-grained locking on the state for record emission.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)