summaryrefslogtreecommitdiff
path: root/db/corruption_test.cc
diff options
context:
space:
mode:
authorhans@chromium.org <hans@chromium.org@62dab493-f737-651d-591e-8d6aee1b9529>2011-06-07 14:40:26 +0000
committerhans@chromium.org <hans@chromium.org@62dab493-f737-651d-591e-8d6aee1b9529>2011-06-07 14:40:26 +0000
commit80e5b0d944b7651046f8b0e795065eca02a01e59 (patch)
treed71e5a056199fd9180f4a1e2a8bddfdd74075a69 /db/corruption_test.cc
parentc4f551494838681f49cc8fb52baaf417d1fea2b1 (diff)
downloadleveldb-80e5b0d944b7651046f8b0e795065eca02a01e59.tar.gz
sync with upstream @21706995
Fixed race condition reported by Dave Smit (dizzyd@dizzyd,com) on the leveldb mailing list. We were not signalling waiters after a trivial move from level-0. The result was that in some cases (hard to reproduce), a write would get stuck forever waiting for the number of level-0 files to drop below its hard limit. The new code is simpler: there is just one condition variable instead of two, and the condition variable is signalled after every piece of background work finishes. Also, all compaction work (including for manual compactions) is done in the background thread, and therefore we can remove the "compacting_" variable. git-svn-id: https://leveldb.googlecode.com/svn/trunk@31 62dab493-f737-651d-591e-8d6aee1b9529
Diffstat (limited to 'db/corruption_test.cc')
0 files changed, 0 insertions, 0 deletions