Thank you Jeff
Regards,
Nitan
Cell: 510 449 9629
> On Jan 23, 2019, at 10:13 AM, Jeff Jirsa wrote:
>
>
>
>> On Jan 23, 2019, at 8:00 AM, Nitan Kainth wrote:
>>
>> Hi,
>>
>> Why does nodetool compactionstats not show time remaining when
>> compactionthroughput is set to 0?
>
> Because we
> On Jan 23, 2019, at 8:00 AM, Nitan Kainth wrote:
>
> Hi,
>
> Why does nodetool compactionstats not show time remaining when
> compactionthroughput is set to 0?
Because we don’t have a good estimate if we’re not throttling (could be added,
just not tracked now)
>
> If the node is restar
Hi,
Why does nodetool compactionstats not show time remaining when
compactionthroughput is set to 0?
If the node is restarted during compaction, does it continue from where it
is left or does it start over?
If it starts over, what happens to the new sstable that was being used for
compaction?
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 result
in SSTables th
> *Reply-To: *"user@cassandra.apache.org"
> *Date: *Sunday, October 23, 2016 at 7:03 PM
> *To: *user
> *Subject: *Re: Question about compaction strategy changes
>
>
>
> More compactions meaning "rows to be compacted" or actual number of
> pending comp
consumed by compaction in a TWCS setting.
From: Seth Edwards
Reply-To: "user@cassandra.apache.org"
Date: Sunday, October 23, 2016 at 7:03 PM
To: user
Subject: Re: Question about compaction strategy changes
More compactions meaning "rows to be compacted" or actu
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 SSTable
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
t
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 number
of SSTable
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!
You were right, Maki. Restarting Cassandra cleaned up the directory and now
there are only two SSTable files.
On Thu, Jul 14, 2011 at 9:08 AM, Maki Watanabe wrote:
> These 0 byte files with "-Compacted" suffix indicate that the
> associated sstables can be removed.
> In current version, Cassandr
These 0 byte files with "-Compacted" suffix indicate that the
associated sstables can be removed.
In current version, Cassandra delete compacted sstables at Full GC and
on startup.
maki
2011/7/14 Sameer Farooqui :
> Running Cassandra 0.8.1. Ran major compaction via:
>
> sudo /home/ubuntu/brisk/r
Running Cassandra 0.8.1. Ran major compaction via:
sudo /home/ubuntu/brisk/resources/cassandra/bin/nodetool -h localhost
compact &
>From what I'd read about Cassandra, I thought that after compaction all of
the different SSTables on disk for a Column Family would be merged into one
new file.
How
13 matches
Mail list logo
