[
https://issues.apache.org/jira/browse/FLINK-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388049#comment-16388049
]
ASF GitHub Bot commented on FLINK-8876:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5645
Making the concurrent access check re-entrant fixes all tests.
My feeling would be to not add an end-to-end test for this, because
end-to-end tests are quite expensive. Is this mainly for validating that this
works by configuring the log level in your opinion?
> 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
(v7.6.3#76005)
