Vamsi Ponnekanti 2b9a360c8b [Getting warning while running db_crashtest] ... Summary: When I run db_crashtest, I am seeing lot of warnings that say db_stress completed before it was killed. To fix that I made ops per thread a very large value so that it keeps running until it is killed. I also set #reopens to 0. Since we are killing the process anyway, the 'simulated crash' that happens during reopen may not add additional value. I usually see 10-25K ops happening before the kill. So I increased max_key from 100 to 1000 so that we use more distinct keys. Test Plan: Ran a few times. Revert Plan: OK Task ID: # Reviewers: emayanke Reviewed By: emayanke CC: leveldb Differential Revision: https://reviews.facebook.net/D9909		2013-04-04 00:17:05 -07:00
..
shell	Titile: a command line shell to read/write data from a leveldb thrift server	2012-08-23 09:41:05 -07:00
db_crashtest.py	[Getting warning while running db_crashtest]	2013-04-04 00:17:05 -07:00
db_repl_stress.cc	Do not allow Transaction Log Iterator to fall ahead when writer is writing the same file	2013-03-06 14:05:53 -08:00
db_stress.cc	Python script to periodically run and kill the db_stress test	2013-04-01 12:18:46 -07:00
ldb_test.py	Fix ldb_test.py to hide garbage from std output	2013-03-12 21:07:07 -07:00
ldb.cc	Integrate the manifest_dump command with ldb	2013-03-22 09:17:30 -07:00
reduce_levels_test.cc	[Rocksdb] codemod NULL to nullptr in tools/*.cc	2013-03-21 10:45:57 -07:00
sst_dump.cc	[Rocksdb] codemod NULL to nullptr in tools/*.cc	2013-03-21 10:45:57 -07:00