Great !!! Thanks Andrei !!! Thats the answer I was looking for :)
Thanks
Anuj Wadehra
Sent from Yahoo Mail on Android
From:"Andrei Ivanov"
Date:Thu, 23 Apr, 2015 at 11:57 pm
Subject:Re: Drawbacks of Major Compaction now that Automatic Tombstone
Compaction Exists
Just in case it helps - we
--
> *From*:"Robert Coli"
> *Date*:Fri, 17 Apr, 2015 at 10:55 pm
> *Subject*:Re: Drawbacks of Major Compaction now that Automatic Tombstone
> Compaction Exists
>
> On Tue, Apr 14, 2015 at 8:29 PM, Anuj Wadehra
> wrote:
>
>> By automatic tombsto
Thanks Robert!!
The JIRA was very helpful in understanding how tombstone threshold is
implemented. And ticket also says that running major compaction weekly is an
alternative. I actually want to understand if I run major compaction on a cf
with 500gb of data and a single giant file is created.
On Tue, Apr 14, 2015 at 8:29 PM, Anuj Wadehra
wrote:
> By automatic tombstone compaction, I am referring to tombstone_threshold
> sub property under compaction strategy in CQL. It is 0.2 by default. So
> what I understand from the Datastax documentation is that even if a sstable
> does not find s
Hi Robert,
Any comments or suggestions ?
Thanks
Anuj Wadehra
Sent from Yahoo Mail on Android
From:"Anuj Wadehra"
Date:Wed, 15 Apr, 2015 at 8:59 am
Subject:Re: Drawbacks of Major Compaction now that Automatic Tombstone
Compaction Exists
Hi Robert,
By automatic tombstone compaction, I am
Hi Robert,
By automatic tombstone compaction, I am referring to tombstone_threshold sub
property under compaction strategy in CQL. It is 0.2 by default. So what I
understand from the Datastax documentation is that even if a sstable does not
find sstables of similar size (STCS) , an automatic t
On Mon, Apr 13, 2015 at 12:26 PM, Rahul Neelakantan wrote:
> Does that mean once you split it back into small ones, automatic
> compaction a will continue to happen on a more frequent basis now that it's
> no longer a single large monolith?
>
That's what the word "size tiered" means in the phras
Rob,
Does that mean once you split it back into small ones, automatic compaction a
will continue to happen on a more frequent basis now that it's no longer a
single large monolith?
Rahul
> On Apr 13, 2015, at 3:23 PM, Robert Coli wrote:
>
>> On Mon, Apr 13, 2015 at 10:52 AM, Anuj Wadehra
>>
On Mon, Apr 13, 2015 at 10:52 AM, Anuj Wadehra
wrote:
> Any comments on side effects of Major compaction especially when sstable
> generated is 100+ GB?
>
I have no idea how this interacts with the automatic compaction stuff; if
you find out, let us know?
But if you want to do a major and don't
Any comments on side effects of Major compaction especially when sstable
generated is 100+ GB?
After Cassandra 1.2 , automated tombstone compaction occurs even on a single
sstable if tombstone percentage increases the tombstone_threshold sub property
specified in compaction strategy. So, even
No.
Anuj Wadehra
On Monday, 13 April 2015 12:23 AM, Sebastian Estevez
wrote:
Have you tried user defined compactions via JMX?On Apr 12, 2015 1:40 PM, "Anuj
Wadehra" wrote:
Recently we faced an issue where every repair operation caused addition of
hundreds of sstables (CASSANDRA
Have you tried user defined compactions via JMX?
On Apr 12, 2015 1:40 PM, "Anuj Wadehra" wrote:
> Recently we faced an issue where every repair operation caused addition of
> hundreds of sstables (CASSANDRA-9146). In order to bring situation under
> control and make sure reads are not impacted, w
12 matches
Mail list logo
