Closed hkparker closed 4 years ago
Reproduced this in an ubuntu docker container using librocksdb-dev
, which is version 5.17.2-3
Seems like it's invalid if there's no data in it. A write just before getting the WAL iterator results in a valid iterator.
In the following trivial example, I attempt to get a WAL iterator on a database using the latest sequence number.
Running this code produces the following:
I've also done more complex examples, where I've loaded some data and the sequence is not 0, but I still get an invalid iterator.
Unless I'm missing something, this seems like a bug in gorocksdb, or rocksdb itself? I'm using arch to install rocksdb, which brought down version 6.5.3-1. Gorocksdb built just fine, but based on this I'm thinking maybe it's a version issue. I'll try to build on an 5.X version and see what happens (though it would be great to be on >= 6.2.2 so I don't have to backport the fix for the memory leak).