You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the case a customer has large partitions - we are going to create a real issue for him (and us) with generating range tombstones that can't be evicted out of the cache and only accumulate - those range tombstones are going to keep pilling up since a compaction of such a table ends up usually with another table that has a large partition as well ...
I think we need to mark the system_large* tables as tables that should not be cached to make sure we do not cause an issue and once we have range tombstones handling made better (and we are working on that) consider removing that.
The text was updated successfully, but these errors were encountered:
The cache of system.large_{partition,rows,cells} accumulates range
tombstones (scylladb#7750), and those
range tombstones can be evicted only together with their partition
(scylladb#3288).
Making the system.large_* tables uncached should work around the
problem until scylladb#3288 is fixed.
Fixesscylladb#8874
Refs scylladb#7750
Refs scylladb#3288
Signed-off-by: Michael Livshin <michael.livshin@scylladb.com>
Message-Id: <20210623171932.8837-1-michael.livshin@scylladb.com>
This issue follows up on #7668 (comment)
@slivne said:
The text was updated successfully, but these errors were encountered: