rocksdb consistency test

[UncP]

trafficstars

Suppose we have 5 rocksdb:

1. generate a series of keys, eg. 100k. The first half is to insert, the other is to delete
2. generate several ranges to perform delete range
3. perform following operations based on above 100k keys and ranges
4. for 50k insert, do a shuffle; for 50k delete, do a shuffle
5. randomly choose from the 100k keys, and insert them in one of three ways: insert, batch insert, ingest sst
6. for the 50k delete, delete them in one of two ways: delete, batch delete
7. do delete range
8. verify that all 5 db are exactly the same, then goto 1

[siddontang]

too many duplicated code with TiKV's, I worry that if we change TiKV's code, we need to not forget to change here.

[UncP]

I tried using tikv as a lib, but that doesn't work, actually tried 2 times. I think later if we add another rocksdb test, we can re-use some code here, so that if tikv changes, we need only change one time.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}