flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8876) Improve concurrent access handling in stateful serializers
Date Wed, 07 Mar 2018 16:42:00 GMT

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

ASF GitHub Bot commented on FLINK-8876:

Github user StephanEwen commented on the issue:

    I added a way to reset the flag into its original state (prior to assertion activation)
and used that to test that the concurrency check is not active by default. The `KryoSerializerConcurrencyTest`
tests the default test setting (concurrency checks on), the `KryoSerializerConcurrencyCheckInactiveITCase`
tests the general default (concurrency checks off).

> Improve concurrent access handling in stateful serializers
> ----------------------------------------------------------
>                 Key: FLINK-8876
>                 URL: https://issues.apache.org/jira/browse/FLINK-8876
>             Project: Flink
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Major
>             Fix For: 1.5.0, 1.6.0
> Some stateful serializers produce incorrect results when accidentally accessed by multiple
threads concurrently.
>  To better catch these cases, I suggest to add concurrency checks that are active only
when debug logging is enabled, and during test runs.
> This is inspired by Kryo's checks for concurrent access.

This message was sent by Atlassian JIRA

View raw message