I'm using Nitrite database to store a million documents and then perform different read operations on them (for benchmarking).
After storing the documents, while trying to read all documents via collection.find().iterator(), I get the following exception:
java.lang.IllegalStateException: Chunk 162 no longer exists [1.4.196/9]
at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:765)
at org.h2.mvstore.MVStore.getChunkIfFound(MVStore.java:953)
at org.h2.mvstore.MVStore.getChunk(MVStore.java:935)
at org.h2.mvstore.MVStore.readPage(MVStore.java:1943)
at org.h2.mvstore.MVMap.readPage(MVMap.java:741)
at org.h2.mvstore.Page.getChildPage(Page.java:217)
at org.h2.mvstore.Cursor.fetchNext(Cursor.java:150)
at org.h2.mvstore.Cursor.next(Cursor.java:50)
at org.dizitart.no2.internals.DocumentCursor$DocumentCursorIterator.nextMatch(DocumentCursor.java:115)
at org.dizitart.no2.internals.DocumentIterator.next(DocumentIterator.java:54)
at org.dizitart.no2.internals.DocumentIterator.next(DocumentIterator.java:32)
...
Then, the next smaller read operations return more values than they should.(Not related to this problem)
I create the database with the default options and three indexes, and it occurs with and without enabled compressing. The used version is 2.1.0.
Is a million documents too much for Nitrite? The same data and test cases work fine with pure MVStore. Inserting only ~340 entries works fine too.
Reactions are currently unavailable
I'm using Nitrite database to store a million documents and then perform different read operations on them (for benchmarking).
After storing the documents, while trying to read all documents via collection.find().iterator(), I get the following exception:
java.lang.IllegalStateException: Chunk 162 no longer exists [1.4.196/9] at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:765) at org.h2.mvstore.MVStore.getChunkIfFound(MVStore.java:953) at org.h2.mvstore.MVStore.getChunk(MVStore.java:935) at org.h2.mvstore.MVStore.readPage(MVStore.java:1943) at org.h2.mvstore.MVMap.readPage(MVMap.java:741) at org.h2.mvstore.Page.getChildPage(Page.java:217) at org.h2.mvstore.Cursor.fetchNext(Cursor.java:150) at org.h2.mvstore.Cursor.next(Cursor.java:50) at org.dizitart.no2.internals.DocumentCursor$DocumentCursorIterator.nextMatch(DocumentCursor.java:115) at org.dizitart.no2.internals.DocumentIterator.next(DocumentIterator.java:54) at org.dizitart.no2.internals.DocumentIterator.next(DocumentIterator.java:32) ...Then, the next smaller read operations return more values than they should.(Not related to this problem)
I create the database with the default options and three indexes, and it occurs with and without enabled compressing. The used version is 2.1.0.
Is a million documents too much for Nitrite? The same data and test cases work fine with pure MVStore. Inserting only ~340 entries works fine too.