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
--
> *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
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 tombstone compaction, I am referring to tombstone_threshold sub
property under compaction strategy in CQL. It is 0.2 by default. So what I
under
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 compac
such issue in prod we can
go ahead with one time major compaction.
Thanks
Anuj Wadehra
From:"Robert Coli"
Date:Tue, 14 Apr, 2015 at 12:54 am
Subject:Re: Drawbacks of Major Compaction now that Automatic Tombstone
Compaction Exists
On Mon, Apr 13, 2015 at 10:52 AM, Anuj Wadehra w
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
are there any disadvantages?
Thanks
Anuj Wadehra
Sent from Yahoo Mail on Android
From:"Anuj Wadehra"
Date:Mon, 13 Apr, 2015 at 12:33 am
Subject:Re: Drawbacks of Major Compaction now that Automatic Tombstone
Compaction Exists
No.
Anuj Wadehra
On Monday, 13 April 2015 12:23 AM,
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
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, we were left with no option but
to run major compaction to ensure that thousands of tiny sstables are
13 matches
Mail list logo
