My guess is that, in Windows, LevelDB is trying to read a file that has been deleted because it was merged with the next level. If you retry the "get" operation or "seek" if you're using a cursor , LevelDB reads from the right sst file. Sadly, yes. At least that worked for me. I don't know if this is fixed in newer versions of leveldb. Ok, this happened to me again, I tried using compactRange after opening the db, and maybe?
El mar. Ok, this happened to me again and in a different context. The same error was thrown when an iterator was not closed after use. Process Explorer showed that the file that throws the error was being held by javaw.
Hope it helps someone. El jue. The problem was solved by closing the iterator which is closeable. In some case my bugged code forgot to close it. I suppose that LevelDB keep the file open until the resource iterator is deallocated. Skip to content. Star Will look into it. I'd guess this is because of the use channel APIs in 32 bit mode instead of the mmap in 64 bit. Can you compare the performance on 32 bit vs 64 bit on your computer?
On 32 bit systems you can add the -Dleveldb. Hitman, if you know your not going to be running out of virtual address space in your use case, use that option. It should speed you up. Skip to content. Star 1. New issue.
Jump to bottom. Copy link. RuntimeException: Could not open table at org. IOException: Map failed at sun. OutOfMemoryError: Map failed at sun. Exception in thread "main" java. File ; import java. Skip to content. Star 2. New issue. Jump to bottom. BasicExample - org. Copy link. Retrying again Nashatyrev closed this Feb 19, Hi Anton, Sorry for the submission, I was afraid it might be something on my end.
Tools: upgrade leveldb to 1. Sign up for free to join this conversation on GitHub. Already have an account?
0コメント