Skip to content

Question about Chunk.MAX_ID #4052

@koljakube

Description

@koljakube

Hello,

I am currently using MVStore as a basis for a simple key-value store in my application. Now I seem to have an irrecoverable store that has a chunk with an id of the value Chunk.MAX_ID, and can not create new chunks. This makes even compacting operations raise exceptions.

Is this expected behavior? I can not find any mechanism that reduces the stored lastChunkId, making it look like every store has a maximum lifetime (due to the limited number of writes possible before reaching this limit).

How am I supposed to work around this? Or better, how does H2 do this, since I understand it uses MVStore for storage and expect this to not mean that every H2 table also eventually breaks.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions