diff --git a/db/db_impl.cc b/db/db_impl.cc index 6ce7a74398516c5ff514be94f6d8ee7e9bd80b24..1241f774302ff3c6abdabeaf929531d32e9cb51c 100644 --- a/db/db_impl.cc +++ b/db/db_impl.cc @@ -2423,7 +2423,7 @@ Status DBImpl::DoCompactionWork(CompactionState* compact, int num_output_files = compact->outputs.size(); if (compact->builder != nullptr) { - // An error occured so ignore the last output. + // An error occurred so ignore the last output. assert(num_output_files > 0); --num_output_files; } diff --git a/doc/index.html b/doc/index.html index 088a73722559ad51a1271e887bc00f5469cb52e1..8c0c9de5a6fef98e0689371a33c65f4427397135 100644 --- a/doc/index.html +++ b/doc/index.html @@ -407,7 +407,7 @@ when 1 write buffer is being flushed to storage, new writes can continue to the other write buffer. Options::min_write_buffer_number_to_merge is the minimum number of write buffers that will be merged together before writing to storage. -If set to 1, then all write buffers are fushed to L0 as individual files and +If set to 1, then all write buffers are flushed to L0 as individual files and this increases read amplification because a get request has to check in all of these files. Also, an in-memory merge may result in writing lesser data to storage if there are duplicate records in each of these @@ -661,7 +661,7 @@ that hold all the different options for that compaction. The exact definition is Here we give short overview of options in CompactionOptionsUniversal: