Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEVERE: java.lang.AssertionError: unknown trans log instruction '0' at log offset: 16 #509

Closed
cszamudio opened this issue May 8, 2015 · 3 comments
Labels

Comments

@cszamudio
Copy link

I started seeing this AssertionError on MapDB version 1.0.7.

May 07, 2015 11:47:01 AM org.mapdb.StoreWAL replayLogFile
SEVERE: java.lang.AssertionError: unknown trans log instruction '0' at log offset: 16

I noticed that this issue was resolved in 1.0.5, but I think it might still be an issue.

I am using a very simple map created as:

db = DBMaker.newFileDB(dbFile)
                .make();

The map has over 2 million simple entries <Integer, Date>
with no concurrent access to the map. The error occurs on the db.commit() statement.

May 07, 2015 11:47:01 AM org.mapdb.StoreWAL replayLogFile
SEVERE: java.lang.AssertionError: unknown trans log instruction '0' at log offset: 16
     at org.mapdb.StoreWAL.replayLogFile(StoreWAL.java:827)
     at org.mapdb.StoreWAL.commit(StoreWAL.java:606)
     at org.mapdb.EngineWrapper.commit(EngineWrapper.java:94)
     at org.mapdb.DB.commit(DB.java:1605)

It's intermittent. The MapDb file is still readable and I can subsequently add and remove to it even after the error is thrown by closing and then re-opening.

@jankotek
Copy link
Owner

It is happening at offset 16, where no data are yet added. My guess is that there is empty commit or file was not synced yet. Will look into this.

@zepernick
Copy link

I have been struggling with this issue intermittently as well. I have multiple threads working off the cache which I think might be part of the problem, but I am not sure. It usually goes away if I synchronize the method that is accessing the cache, but this really hinders my performance. I have tried putting synchronize blocks inside the method instead, but I have not been able to get that right because it still pops up every now and then.

@jankotek
Copy link
Owner

jankotek commented Aug 7, 2015

Can not replicate, please use 2.0 branch.

@jankotek jankotek closed this as completed Aug 7, 2015
bazi added a commit to subutai-attic/kurjun that referenced this issue Feb 3, 2016
doing empty commits may causes issues like mentioned in
jankotek/mapdb#509
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants