Re: Node Size

his is for on-prem hardware, not a cloud-there’s-always-a-spare model.) Sean Durity *From:* Jeff Jirsa *Sent:* Wednesday, January 20, 2021 11:59 AM *To:* cassandra *Subject:* [EXTERNAL] Re: Node Size Not going to give a number other than to say that 1TB/instance is probably super s

RE: Node Size

: Jeff Jirsa Sent: Wednesday, January 20, 2021 11:59 AM To: cassandra Subject: [EXTERNAL] Re: Node Size Not going to give a number other than to say that 1TB/instance is probably super super super conservative in 2021. The modern number is likely considerably higher. But let's look at this

Re: Node Size

it, yet, but I will be testing it soon. In my > understanding it is for use cases with massive needs for disk, but low to > moderate throughput (ie, where node expansion is only for disk, not > additional traffic). > > > > Sean Durity > > > > *From:* Yakir Gibraltar &g

Re: Node Size

with massive needs for disk, but low to moderate throughput (ie, where node expansion is only for disk, not additional traffic). Sean Durity *From:* Yakir Gibraltar *Sent:* Wednesday, January 20, 2021 9:21 AM *To:* user@cassandra.apache.org *Subject:* [EXTERNAL] Re: Node Size It possible t

RE: Node Size

From: Yakir Gibraltar Sent: Wednesday, January 20, 2021 9:21 AM To: user@cassandra.apache.org Subject: [EXTERNAL] Re: Node Size It possible to use large nodes and it will work, the problem of large nodes will be: * Maintenance like join/remove nodes will take more time. * Larger heap

Re: Node Size

ould find out more information on this? > Thanks! > > -Joe > > On 1/13/2021 8:42 AM, Joe Obernberger wrote: > > Reading the documentation on Cassandra 3.x there is recommendations > > that node size should be ~1TByte of data. Modern servers can have 24 > > SSDs, ea

Re: Node Size

Anyone know where I could find out more information on this? Thanks! -Joe On 1/13/2021 8:42 AM, Joe Obernberger wrote: Reading the documentation on Cassandra 3.x there is recommendations that node size should be ~1TByte of data.  Modern servers can have 24 SSDs, each at 2TBytes in size for

Node Size

Reading the documentation on Cassandra 3.x there is recommendations that node size should be ~1TByte of data.  Modern servers can have 24 SSDs, each at 2TBytes in size for data.  Is that a bad idea for Cassandra?  Does 4.0beta4 handle larger nodes? We have machines that have 16, 8TBytes SATA

Re: Cassandra 2.1.12 Node size

% disk issue. I recently ran the cleanup and backups aren't taking that much space. On Thu, Apr 14, 2016 at 8:06 PM, Jack Krupansky wrote: > The four criteria I would suggest for evaluating node size: > > 1. Query latency. > 2. Query throughput/load > 3. Repair time - worst cas

Re: Cassandra 2.1.12 Node size

The four criteria I would suggest for evaluating node size: 1. Query latency. 2. Query throughput/load 3. Repair time - worst case, full repair, what you can least afford if it happens at the worst time 4. Expected growth over the next six to 18 months - you don't what to be scrambling

Re: Cassandra 2.1.12 Node size

> > Would adding nodes be the right way to start if I want to get the data per > node down Yes, if everything else is fine, the last and always available option to reduce the disk size per node is to add new nodes. Sometimes it is the first option considered as it is relatively quick and quite st

Re: Cassandra 2.1.12 Node size

Thanks for the response Alain. I am using STCS and would like to take some action as we would be hitting 50% disk space pretty soon. Would adding nodes be the right way to start if I want to get the data per node down otherwise can you or someone on the list please suggest the right way to go ab

Re: Cassandra 2.1.12 Node size

Hi, I seek advice in data size per node. Each of my node has close to 1 TB of > data. I am not seeing any issues as of now but wanted to run it by you guys > if this data size is pushing the limits in any manner and if I should be > working on reducing data size per node. There is no real limit

Cassandra 2.1.12 Node size

Hi all, I am running a 9 node C* 2.1.12 cluster. I seek advice in data size per node. Each of my node has close to 1 TB of data. I am not seeing any issues as of now but wanted to run it by you guys if this data size is pushing the limits in any manner and if I should be working on reducing data si

Re: Practical node size limits

> The bottleneck now seems to be the repair time. If any node becomes too > inconsistent, or needs to be replaced, the rebuilt time is over a week. This is why i've recommended 300GB to 400GB per node in the past. It's not a hard limit, but it seems to be a nice balance. You need to take into c

Re: Practical node size limits

This is actually another problem that we've encountered with Cassandra; the range of platforms it can be deployed on is fairly limited. If you want to run with Oracle's JRE (which is apparently recommended), you are pretty much stuck with Linux on x86/64 (I haven't tried the new JDK on ARM yet,

Re: Practical node size limits

On Sun, Jul 29, 2012 at 7:40 PM, Dustin Wenz wrote: > We've just set up a new 7-node cluster with Cassandra 1.1.2 running under > OpenJDK6. It's worth noting that Cassandra project recommends Sun JRE. Without the Sun JRE, you might not be able to use JAMM to determine the live ratio. Very few pe

Re: Practical node size limits

You can try increasing streaming throttle. 2012/9/4 Dustin Wenz > I'm following up on this issue, which I've been monitoring for the last > several weeks. I thought people might find my observations interesting. > > Ever since increasing the heap size to 64GB, we've had no OOM conditions > that

Re: Practical node size limits

I'm following up on this issue, which I've been monitoring for the last several weeks. I thought people might find my observations interesting. Ever since increasing the heap size to 64GB, we've had no OOM conditions that resulted in a JVM termination. Our nodes have around 2.5TB of data each, a

Re: Practical node size limits

On Mon, Jul 30, 2012 at 2:04 PM, Dustin Wenz wrote: > CFStats reports that the bloom filter size is currently several gigabytes Just so you know, you can control bloom filter sizes now with the per-cf bloom_filter_fp_chance attribute. -- Tyler Hobbs DataStax

Re: Practical node size limits

Thanks for the pointer! It sounds likely that's what I'm seeing. CFStats reports that the bloom filter size is currently several gigabytes. Is there any way to estimate how much heap space a repair would require? Is it a function of simply adding up the filter file sizes, plus some fraction of n

Re: Practical node size limits

Yikes. You should read: http://wiki.apache.org/cassandra/LargeDataSetConsiderations Essentially what it sounds like your are now running into is this: The BloomFilters for each SSTable must exist in main memory. Repair tends to create some extra data which normally gets compacted away later. Yo

Practical node size limits

I'm trying to determine if there are any practical limits on the amount of data that a single node can handle efficiently, and if so, whether I've hit that limit or not. We've just set up a new 7-node cluster with Cassandra 1.1.2 running under OpenJDK6. Each node is 12-core Xeon with 24GB of RA

Re: cassandra crashed while repairing, leave node size X3

got it, thanks! On Tue, Sep 20, 2011 at 12:27 AM, Peter Schuller < peter.schul...@infidyne.com> wrote: > > In my tests I have seen repair sometimes take a lot of space (2-3 times), > > cleanup did not clean it, the only way I could clean that was using major > > compaction. > > https://issues.apa

Re: cassandra crashed while repairing, leave node size X3

> In my tests I have seen repair sometimes take a lot of space (2-3 times), > cleanup did not clean it, the only way I could clean that was using major > compaction. https://issues.apache.org/jira/browse/CASSANDRA-2816 (follow links to other jiras) https://issues.apache.org/jira/browse/CASSANDRA-2

Re: cassandra crashed while repairing, leave node size X3

I am using 0.7.4 too. and would waiting for 0.8.6 stable to release because of CASSANDRA-3166. did you already using 0.8.6 in production? 2011/9/19 Jonas Borgström > On 09/19/2011 04:26 AM, Anand Somani wrote: > > In my tests I have seen repair sometimes take a lot of space (2-3 > > times), cle

Re: cassandra crashed while repairing, leave node size X3

On 09/19/2011 04:26 AM, Anand Somani wrote: > In my tests I have seen repair sometimes take a lot of space (2-3 > times), cleanup did not clean it, the only way I could clean that was > using major compaction. Do you remember with what version you saw these problems? I've had the same problems wi

Re: cassandra crashed while repairing, leave node size X3

so does major compaction actually "clean it" or "merge it", I am afraid it give me a single large file On Mon, Sep 19, 2011 at 10:26 AM, Anand Somani wrote: > In my tests I have seen repair sometimes take a lot of space (2-3 times), > cleanup did not clean it, the only way I could clean that

Re: cassandra crashed while repairing, leave node size X3

In my tests I have seen repair sometimes take a lot of space (2-3 times), cleanup did not clean it, the only way I could clean that was using major compaction. On Sun, Sep 18, 2011 at 6:51 PM, Yan Chunlu wrote: > while doing repair on node3, the "Load" keep increasing, suddenly cassandra > has e

cassandra crashed while repairing, leave node size X3

while doing repair on node3, the "Load" keep increasing, suddenly cassandra has encountered OOM, and the "Load" stopped at 140GB, after cassandra came back, I tried node cleanup but it seems not working does node repair generate many temp sstables? how to get rid of them? thanks! Address