Don't score a rolling file
In giving an empty file a score of 0, a race condition was exposed. A file might not be active, but might still be rolling - and then cna get scored as 0, and immediately compacted. It will then be removed from the journal manifest. Check each file is not rolling before making it a candidate for rolling.
This commit is contained in:
parent
5f7d261a87
commit
808a858d09
2 changed files with 6 additions and 2 deletions
|
@ -905,7 +905,7 @@ handoff(_Config) ->
|
|||
{sync_strategy, sync}],
|
||||
{ok, Bookie1} = leveled_bookie:book_start(StartOpts1),
|
||||
|
||||
% Add some noe Riak objects in - which should be ignored in folds.
|
||||
% Add some none Riak objects in - which should be ignored in folds.
|
||||
Hashes = testutil:stdload(Bookie1, 1000),
|
||||
% Generate 200K objects to be used within the test, and load them into
|
||||
% the first store (outputting the generated objects as a list of lists)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue