You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Yun Tang (JIRA)" <ji...@apache.org> on 2018/08/30 17:30:00 UTC

[jira] [Created] (FLINK-10267) [State] Fix arbitrary iterator access on RocksDBMapIterator

Yun Tang created FLINK-10267:
--------------------------------

             Summary: [State] Fix arbitrary iterator access on RocksDBMapIterator
                 Key: FLINK-10267
                 URL: https://issues.apache.org/jira/browse/FLINK-10267
             Project: Flink
          Issue Type: Bug
          Components: State Backends, Checkpointing
    Affects Versions: 1.6.0, 1.5.3
            Reporter: Yun Tang
            Assignee: Yun Tang
             Fix For: 1.6.1, 1.5.4


Currently, RocksDBMapIterator would load 128 entries into local cacheEntries. Both RocksDBMapIterator#next() and RocksDBMapIterator#hasNext() action would trigger to load RocksDBEntry into cacheEntries.

However, if the iterator's size larger than 128 and we continue to access the iterator with following order: hasNext() -> next() -> hasNext() -> remove(), we would meet weird exception when we try to remove the 128th element:
{code:java}
java.lang.IllegalStateException: The remove operation must be called after a valid next operation.
{code}
Since we could not control user's access on iterator, we should fix this bug to avoid unexpected exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)