[
https://issues.apache.org/jira/browse/FLINK-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388266#comment-16388266
]
ASF GitHub Bot commented on FLINK-8876:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/5645
The end-to-end test would be cheap as we wouldn't execute a flink job or
even start a flink cluster.
The scripts in `flink-end-to-end-tests` can do pretty much anything they
want; my idea was to just call the test method in a non-test context, in which
case the test should throw an AssertionError. It may not be the cleanest thing
to do though as we have to max test and production code in a single jar.
My goal was to verify that the sections guarded by
`CONCURRENT_ACCESS_CHECK` are skipped at runtime by default. As it stands
someone could just hard-code it to `true` and there's no test preventing that.
> 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)
