[
https://issues.apache.org/jira/browse/FLINK-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826501#comment-15826501
]
ASF GitHub Bot commented on FLINK-5530:
---------------------------------------
GitHub user NicoK opened a pull request:
https://github.com/apache/flink/pull/3143
[FLINK-5530] fix race condition in AbstractRocksDBState#getSerializedValue
`AbstractRocksDBState#getSerializedValue()` uses the same key serialisation
stream as the ordinary state access methods but is called in parallel during
state queries thus violating the assumption of only one thread accessing it.
This may lead to either wrong results in queries or corrupt data while
queries
are executed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NicoK/flink flink-5530
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3143.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3143
----
commit 7fa4c61a04cb96b94907e6ec3803b994d3c6643d
Author: Nico Kruber <n...@data-artisans.com>
Date: 2017-01-17T16:38:29Z
[FLINK-5530] fix race condition in AbstractRocksDBState#getSerializedValue
AbstractRocksDBState#getSerializedValue() uses the same key serialisation
stream as the ordinary state access methods but is called in parallel during
state queries thus violating the assumption of only one thread accessing it.
This may lead to either wrong results in queries or corrupt data while
queries
are executed.
----
> race condition in AbstractRocksDBState#getSerializedValue
> ---------------------------------------------------------
>
> Key: FLINK-5530
> URL: https://issues.apache.org/jira/browse/FLINK-5530
> Project: Flink
> Issue Type: Bug
> Components: Queryable State
> Affects Versions: 1.2.0
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Blocker
>
> AbstractRocksDBState#getSerializedValue() uses the same key serialisation
> stream as the ordinary state access methods but is called in parallel during
> state queries thus violating the assumption of only one thread accessing it.
> This may lead to either wrong results in queries or corrupt data while
> queries are executed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
