[jira] [Commented] (FLINK-27311) Rocksdb mapstate behaves unexpectedly

["Yun Tang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-27311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524691#comment-17524691 ] 

Yun Tang commented on FLINK-27311:
----------------------------------

[~JonathanDiamant] , what do you mean for {{"it seems that not all the list corresponding to a certain key has been loaded and only after all the state has been recovered it behaves as expected"}}?

Before the restore phase is compeleted, the state cannot be accessed.

> Rocksdb mapstate behaves unexpectedly 
> --------------------------------------
>
>                 Key: FLINK-27311
>                 URL: https://issues.apache.org/jira/browse/FLINK-27311
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / State Backends, Stateful Functions
>    Affects Versions: 1.14.4
>         Environment: Kubernetes
>            Reporter: Jonathan diamant
>            Priority: Major
>              Labels: MapState, State, rocksdb
>
> We use rocksDb backend for our state and we experience an unexpected behavior. The state we use is MapState<String, List<Object>> and when a restart occurs and the state is being recovered from the last checkpoints, it seems that not all the list corresponding to a certain key has been loaded and only after all the state has been recovered it behaves as expected. 
> Our guess is that while recovering the state, rocksdb recovers the state in chunks and loads entries of the map not as a whole even though we expect that for every key, the value (a list) will be loaded as one object at once.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)