After upgrading grocksdb from v1.8.12 to v1.9.3, I noticed that some statistics values appeared abnormal.
For example, I found the value of rocksdb.compact.write.bytes in the LOG file (periodically dumped stats) showed it as 278576274:
$ grep rocksdb.compact.write.bytes LOG
rocksdb.compact.write.bytes COUNT : 0
rocksdb.compact.write.bytes COUNT : 115702019
rocksdb.compact.write.bytes COUNT : 278576274
However, the value retreived using opts.GetTickerCount() remained at 539.
Interestingly, the value for rocksdb.db.iter.bytes.read was exactly 539, leading I to suspect that the statistics might have been incorrectly mapped.
After upgrading grocksdb from v1.8.12 to v1.9.3, I noticed that some statistics values appeared abnormal.
For example, I found the value of
rocksdb.compact.write.bytesin the LOG file (periodically dumped stats) showed it as 278576274:However, the value retreived using
opts.GetTickerCount()remained at 539.Interestingly, the value for
rocksdb.db.iter.bytes.readwas exactly 539, leading I to suspect that the statistics might have been incorrectly mapped.