[
https://issues.apache.org/jira/browse/FLINK-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328833#comment-17328833
]
Flink Jira Bot commented on FLINK-5730:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> 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
> Components: Runtime / State Backends
> Reporter: Stefan Richter
> Priority: Major
> Labels: stale-major
>
> 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
(v8.3.4#803005)
