mirrors/scylladb
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

truncate: do not flush memtables if auto_snapshot is false.

Browse Source 
Right now we flush memtables if the table is durable (which in practice
it almost always is).

We are truncating, so we don't want the data. We should only flush if
auto_snapshot is true.

Signed-off-by: Glauber Costa <glauber@scylladb.com>
This commit is contained in:
Glauber Costa
2019-02-27 15:09:57 -05:00
parent ed8261a0fe
commit c2c6c71398
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
database.cc
View File

@@ -1683,9 +1683,8 @@ future<> database::truncate(sstring ksname, sstring cfname, timestamp_func tsf)
future<> database::truncate(const keyspace& ks, column_family& cf, timestamp_func tsf, bool with_snapshot) {
return cf.run_async([this, &ks, &cf, tsf = std::move(tsf), with_snapshot] {
const auto durable = ks.metadata()->durable_writes();
const auto auto_snapshot = with_snapshot && get_config().auto_snapshot();
const auto should_flush = durable || auto_snapshot;
const auto should_flush = auto_snapshot;
// Force mutations coming in to re-acquire higher rp:s
// This creates a "soft" ordering, in that we will guarantee that