n bootstrap process
>
> Thanks Alain.We are using C* 2.1.18,7core/30G/1.5T ssd,as the cluster is
> growing too fast,we are painful in bootstrap/rebuild/remove node.
>
> Thanks,
> Peng Xiao
>
> -- 原始邮件 --
> *发件人:* "Alain RODRIGUEZ";
>
Hello,
> Is it reasonable to disable compaction on all the source node?
I would say no, as a short answer.
You can, I did it for some operations in the past. Technically no problem
you can do that. It will most likely improve the response time of the
queries immediately as it seems that in you
Thanks for all replies and Date Tiered strategy sounds good to me. I am
still using 2.0x version and will consider updating to latest version.
On Fri, Apr 8, 2016 at 11:20 PM, Eric Stevens wrote:
> Append-only workloads are a good candidate for Date Tiered or better Time
> Windowed compaction.
Append-only workloads are a good candidate for Date Tiered or better Time
Windowed compaction. Effectively depending on how you set it up, data in
older SStables will eventually come to rest and never be compacted again.
On Fri, Apr 8, 2016 at 7:42 AM Robert Wille wrote:
> You still need compac
You still need compaction. Compaction is what organizes your data into levels.
Without compaction, every query would have to look at every SSTable.
Also, due to commit log rotation, your memtable may get flushed from time to
time before it is full, resulting in small SSTables that would benefit
I am using leveled strategy. What if my data are 'append-only'? I mean
there are always new data but will be never changed once written to
cassandra?
On Fri, Apr 8, 2016 at 6:33 PM, Pedro Gordo
wrote:
> Hi Yatong
>
> My understanding is that if you have a table whichi read-only and hence
> doesn
Hi Yatong
My understanding is that if you have a table whichi read-only and hence
doesn't receive any writes, then no SSTables will be created, and hence, no
compaction will happen. What compaction strategy do you have on your table?
Best regards
Pedro Gordo
On 8 April 2016 at 10:42, Yatong Zha
If you are using sized teired set minCompactionThreshold to 0 and
maxCompactionThreshold to 0. You can probably also use this
https://issues.apache.org/jira/browse/CASSANDRA-2130
But if you do not compact the number of sstables gets high and then
read performance can suffer.
On Sat, Oct 27, 2012
Thanx a lot Edward, will follow your advice.
On Wed, Jul 20, 2011 at 7:28 PM, Edward Capriolo wrote:
>
>
> On Wed, Jul 20, 2011 at 11:13 AM, Nikolai Kopylov wrote:
>
>> Hi everyone,
>>
>> finding out recently that cassandra have no upper limit for sstable files
>> to grow, I decided to move to de
On Wed, Jul 20, 2011 at 11:13 AM, Nikolai Kopylov wrote:
> Hi everyone,
>
> finding out recently that cassandra have no upper limit for sstable files
> to grow, I decided to move to deletion of CF with obsolete data.
> So that I will not remove columns and there is no need in compaction at
> all.
10 matches
Mail list logo
