Raphael S. Carvalho a214ccdf89 sstables/compaction: Don't invalidate row cache when adding GC SSTable to SSTable set ...

Garbage collected SSTable is incorrectly added to SSTable set with a function
that invalidates row cache. This problem is fixed by adding GC SStable
to set using mechanism which replaces old sstables with new sstables.

Also, adding GC SSTable to set in a separate call is not correct.
We should make sure that GC SSTable reaches the SSTable set at the same time
its respective old (input) SSTable is removed from the set, and that's done
using a single request call to table.

Fixes #5956.
Fixes #6275.

Signed-off-by: Raphael S. Carvalho <raphaelsc@scylladb.com>

2020-05-05 12:03:19 -03:00

..

alternator

alternator: fix checking max item depth

2020-05-04 23:46:20 +03:00

boost

sstables/compaction: Don't invalidate row cache when adding GC SSTable to SSTable set

2020-05-05 12:03:19 -03:00

cql

cql/tests: Added test for filtering on counter columns

2020-04-27 13:36:16 +02:00

lib

messaging_service: Use reloadable TLS certificates

2020-05-04 11:32:21 +00:00

manual

versioned_value: remove versioned_value::factory class

2020-04-20 12:57:16 +02:00

perf

treewide: use thread-safe variant of localtime

2020-05-04 14:46:08 +03:00

resource

sstables: freeze types nested in collection types in legacy sstables

2020-04-16 18:44:56 +03:00

tools

treewide: replace calls to engine().some_api() with some_api()

2020-04-05 12:46:04 +03:00

unit

row_cache_alloc_stress_test: Make sure GCC can't delete a new

2020-04-26 15:22:04 +03:00