You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stefan Richter (JIRA)" <ji...@apache.org> on 2017/02/07 09:32:41 UTC

[jira] [Updated] (FLINK-5730) Users can concurrently modify state metadata of RocksDB asynchronous snapshots

     [ https://issues.apache.org/jira/browse/FLINK-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Richter updated FLINK-5730:
----------------------------------
    Summary: Users can concurrently modify state metadata of RocksDB asynchronous snapshots  (was: User can concurrently modify state metadata of RocksDB asynchronous snapshots)

> Users can concurrently modify state metadata of RocksDB asynchronous snapshots
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-5730
>                 URL: https://issues.apache.org/jira/browse/FLINK-5730
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Stefan Richter
>
> The current implementation of asynchronous snapshots in RocksDB iterates the original state metadata structures as part of the asynchronous snapshot. Users could potentially modify the state metadata concurrently (e.g. by registering a new state while the snapshot is running), thereby corrupting the metadata.
> For the way most users are registering their states (at the start of the task), this is not a problem. However, if state is conditionally registered at some later point in time this can be problematic.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)