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

Posted to issues@flink.apache.org by "Jiangjie Qin (JIRA)" <ji...@apache.org> on 2019/07/11 07:46:00 UTC

[jira] [Closed] (FLINK-13204) The subscribedPartitionStates should be thread safe.

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

Jiangjie Qin closed FLINK-13204.
--------------------------------
    Resolution: Duplicate

I was looking at an outdated code base and the issue has been fixed in release 1.4.3 and 1.5.0.

> The subscribedPartitionStates should be thread safe.
> ----------------------------------------------------
>
>                 Key: FLINK-13204
>                 URL: https://issues.apache.org/jira/browse/FLINK-13204
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka
>            Reporter: Jiangjie Qin
>            Assignee: Jiangjie Qin
>            Priority: Major
>
> The \{{subscribedPartitionState}} should be thread safe. This variable may be modified by the partition discoverer thread while being read by the main thread. So when subscribed partition changes (e.g. partition expansion, new topic matching the pattern is created), a \{{ConcurrentModificationException}} may be thrown.
> The fix is to use the set from a {{ConcurrentHashMap}} instead of a \{{List}} for \{{subscribedPartitionState}}.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)