On 24 October 2016 at 18:11, Seth Edwards wrote:
> The other thought is that we currently have data mixed in that does not
> have a TTL and we are strongly considering putting this data in it's own
> table.
You should definitely do that. Having non-TTL'd data mixed in will
rds <s...@pubnub.com>
> *Reply-To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
> *Date: *Sunday, October 23, 2016 at 7:03 PM
> *To: *user <user@cassandra.apache.org>
> *Subject: *Re: Question about compaction strategy changes
>
>
>
>
consumed by compaction in a TWCS setting.
From: Seth Edwards <s...@pubnub.com>
Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Sunday, October 23, 2016 at 7:03 PM
To: user <user@cassandra.apache.org>
Subject: Re: Question about compacti
​More compactions meaning "actual number of compaction tasks". A compaction
task generally operates on many SSTables (how many depends on the chosen
compaction strategy). The number of pending tasks does not line up with the
number of SSTables that will be compacted. 1 task may compact many
More compactions meaning "rows to be compacted" or actual number of pending
compactions? I assumed when I run nodetool compactionstats the number of
pending tasks would line up with number of sstables that will be compacted.
Most of the time this is idle, then we hit spots when it could jump into
On 22 October 2016 at 03:37, Seth Edwards wrote:
> We're using TWCS and we notice that if we make changes to the options to
> the window unit or size, it seems to implicitly start recompacting all
> sstables.
If you increase the window unit or size you potentially increase the
Hello! We're using TWCS and we notice that if we make changes to the
options to the window unit or size, it seems to implicitly start
recompacting all sstables. Is this indeed the case and more importantly,
does the same happen if we were to adjust the gr_grace_seconds for this
table?
Thanks!