[ https://issues.apache.org/jira/browse/IGNITE-23389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908191#comment-17908191 ]
Roman Puchkovskiy commented on IGNITE-23389: -------------------------------------------- According to [https://github.com/facebook/rocksdb/blob/main/include/rocksdb/listener.h#L183] , it's kWalFull, so we have a WAL and were not able to flush to disk. I'm just guessing, but inability to flush might block WAL truncation, so this might look as a deadlock. Here, [https://github.com/facebook/rocksdb/blob/main/java/src/main/java/org/rocksdb/FlushReason.java#L20] it can be seen that only values up to 12 are supported in Java part. It seems that Rocks Java integration has to be fixed. > Illegal flush reason 13 > ----------------------- > > Key: IGNITE-23389 > URL: https://issues.apache.org/jira/browse/IGNITE-23389 > Project: Ignite > Issue Type: Bug > Reporter: Vladislav Pyatkov > Priority: Major > Labels: ignite-3 > Attachments: InsertBenchmark.java > > > h3. Motivation > It is difficult to realise what the stack means, but any stack exception in > the log looks suspective. > {noformat} > java.lang.IllegalArgumentException: Illegal value provided for FlushReason: 13 > at org.rocksdb.FlushReason.fromValue(FlushReason.java:51) > at org.rocksdb.FlushJobInfo.<init>(FlushJobInfo.java:41) > {noformat} > I got this stack in the benchmark attached below. > h3. Definition of done > This stack ought to not appear in the log. -- This message was sent by Atlassian Jira (v8.20.10#820010)