You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jonathan diamant (Jira)" <ji...@apache.org> on 2022/04/19 10:39:00 UTC

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

Jonathan diamant created FLINK-27311:
----------------------------------------

             Summary: Rocksdb mapstate behaves unexpectedly 
                 Key: FLINK-27311
                 URL: https://issues.apache.org/jira/browse/FLINK-27311
             Project: Flink
          Issue Type: Technical Debt
          Components: Runtime / State Backends, Stateful Functions
    Affects Versions: 1.14.4
         Environment: Kubernetes
            Reporter: Jonathan diamant
             Fix For: 1.14.5


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.1#820001)