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
> d
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
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
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,
f 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 compacted.
Queries:
Does major compaction has any drawback after automatic tombstone comp
ds are not impacted, we were left with no option
> but to run major compaction to ensure that thousands of tiny sstables are
> compacted.
>
> Queries:
> Does major compaction has any drawback after automatic tombstone
> compaction got implemented in 1.2 via tombstone_threshol
compacted.
Queries:
Does major compaction has any drawback after automatic tombstone compaction got
implemented in 1.2 via tombstone_threshold sub-property(CASSANDRA-3442)?
I understand that the huge SSTable created after major compaction wont be
compacted with new data any time soon but is
t;> I ran upgradesstables as part of the Cassandra upgrade, before issuing
>>the
>> CQL alter command.
>>
>> According to the docs, SizeTieredCompactionStrategy is fine (that is
>>what I
>> used, and plan on continue using), and automatic tombstone compac
Subject: Re: Automatic tombstone compaction
In the context of Yuki's response, if you are using the same key for the cache,
then your rows will get increasingly fragmented.
On Wed, Aug 21, 2013 at 1:09 PM,
mailto:tamas.fold...@thomsonreuters.com>>
wrote:
Well, these tables are somewhat
ventbrite.com]
> *Sent:* Wednesday, August 21, 2013 7:45 PM
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: Automatic tombstone compaction
>
> On Wed, Aug 21, 2013 at 8:23 AM, Yuki Morishita wrote:
>
>> If there are rows with the same key in other SSTables, that ro
e setup is correct - i.e the ALTER statement I
quoted below?
Also, I the docs were not clear to me - is automatic tombstone compaction 'on'
by default (even if the sstables have been migrated from an older version)? Or
do I need to alter the columnfamily (like
On Wed, Aug 21, 2013 at 8:23 AM, Yuki Morishita wrote:
> If there are rows with the same key in other SSTables, that rows won't
> be deleted.
> Tombstone compaction make guess if it can actually drop "safely" by
> scanning overlap with other SSTables.
>
Background @ :
https://issues.apache.org/
erwise it would
> not accept my command.
>
> Is that not right?
>
>
>
> Thanks,
>
> Tamas
>
>
>
> From: Haithem Jarraya [mailto:a-hjarr...@expedia.com]
> Sent: 21. august 2013 16:24
> To: user@cassandra.apache.org
> Subject: Re: Automatic tombstone co
sstables as part of the Cassandra upgrade, before issuing the CQL
alter command.
According to the docs, SizeTieredCompactionStrategy is fine (that is what I
used, and plan on continue using), and automatic tombstone compaction is
available for it:
http://www.datastax.com/documentation/cassandra/
Hi,
I ran upgradesstables as part of the Cassandra upgrade, before issuing the CQL
alter command.
According to the docs, SizeTieredCompactionStrategy is fine (that is what I
used, and plan on continue using), and automatic tombstone compaction is
available for it:
http://www.datastax.com
e:
Hi,
After upgrading from 1.0 to 1.2, I wanted to make use of the automatic
tombstone compaction feature, so using CQL3 I issued:
ALTER TABLE versions WITH compaction = {'class' :
'SizeTieredCompactionStrategy', 'min_threshold' : 4, 'max_threshold&#x
Hi,
After upgrading from 1.0 to 1.2, I wanted to make use of the automatic
tombstone compaction feature, so using CQL3 I issued:
ALTER TABLE versions WITH compaction = {'class' :
'SizeTieredCompactionStrategy', 'min_threshold' : 4, 'max_threshold' :
23 matches
Mail list logo
