In this page, we summarize some known issues and limitations that RocksDB users need to know:

• rocksdb::DB instances need to be destroyed before your main function exits. RocksDB instances usually depend on some internal static variables. Users need to make sure rocksdb::DB instances are destroyed before those static variables.

• Universal Compaction Style has a limitation on total data size. See Universal Compaction.

• Some features are not supported in RocksJava, See RocksJava Basics. If there is a feature in the C++ API which is missing from the Java API that you need, please open an issue with a feature request.

• If you use prefix iterating and iterates out of the prefix range, by running Prev() will not recover from the previous key and the results are undefined.

• If you use prefix iterating and you are changing iterating order, Seek()->Prev() or Next()->Prev(), you may not get correct results.

• Atomicity is not guaranteed after DB recovery for more than one multiple column families and WAL is disabled.