flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kostas Kloudas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6007) ConcurrentModificationException in WatermarkCallbackService
Date Thu, 09 Mar 2017 16:13:38 GMT

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

Kostas Kloudas commented on FLINK-6007:

[~aljoscha] Now that I come to think about it, this solution assumes that 2 x noOfKeys fit
in memory. 
The size of the deletion set is at most equal to the set of the registered keys. 
Given this, I am not sure if the second solution is the best

> ConcurrentModificationException in WatermarkCallbackService
> -----------------------------------------------------------
>                 Key: FLINK-6007
>                 URL: https://issues.apache.org/jira/browse/FLINK-6007
>             Project: Flink
>          Issue Type: Bug
>          Components: DataStream API
>    Affects Versions: 1.3.0
>            Reporter: Kostas Kloudas
>            Assignee: Kostas Kloudas
>            Priority: Blocker
>             Fix For: 1.3.0
> Currently, if an attempt is made to call {{InternalWatermarkCallbackService.unregisterKeyFromWatermarkCallback()}}
from within the {{OnWatermarkCallback}}, a {{ConcurrentModificationException}} is thrown.
The reason is that the {{invokeOnWatermarkCallback}} iterates over the list of keys and calls
the callback for each one of them.
> To fix this, the deleted keys are put into a separate list, and the deletion happens
after the iteration over all keys has finished.

This message was sent by Atlassian JIRA

View raw message