in advance.
Wade
From: aaron morton
[mailto:aa...@thelastpickle.commailto:aa...@thelastpickle.com]
Sent: Wednesday, December 05, 2012 9:23 PM
To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Re: Freeing up disk space on Cassandra 1.1.5 with Size-Tiered
compaction.
Basically we
@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: RE: Freeing up disk space on Cassandra 1.1.5 with Size-Tiered
compaction.
So if my calculations are correct a terabyte sized database would require a
minimum of 15 nodes (RF = 3). That sound about right?
2000 / 400 * RF
From: aaron
duh, sorry. That estimate is 2 TB would be 15 nodes rf = 3
From: Poziombka, Wade L [mailto:wade.l.poziom...@intel.com]
Sent: Friday, December 07, 2012 7:15 AM
To: user@cassandra.apache.org
Subject: RE: Freeing up disk space on Cassandra 1.1.5 with Size-Tiered
compaction.
So if my calculations
To: user@cassandra.apache.org
Subject: Re: Freeing up disk space on Cassandra 1.1.5 with Size-Tiered
compaction.
Basically we were successful on two of the nodes. They both took ~2 days and 11
hours to complete and at the end we saw one very large file ~900GB and the rest
much smaller
node. But this 300-400MB business is interesting to me.
** **
Thanks in advance.
** **
Wade
** **
*From:* aaron morton [mailto:aa...@thelastpickle.com]
*Sent:* Wednesday, December 05, 2012 9:23 PM
*To:* user@cassandra.apache.org
*Subject:* Re: Freeing up disk space
]
Sent: Wednesday, December 05, 2012 9:23 PM
To: user@cassandra.apache.org
Subject: Re: Freeing up disk space on Cassandra 1.1.5 with Size-Tiered
compaction.
Basically we were successful on two of the nodes. They both took ~2 days and
11 hours to complete and at the end we saw one very
, December 05, 2012 9:23 PM
To: user@cassandra.apache.org
Subject: Re: Freeing up disk space on Cassandra 1.1.5 with Size-Tiered
compaction.
Basically we were successful on two of the nodes. They both took ~2 days and 11
hours to complete and at the end we saw one very large file ~900GB
Subject: RE: Freeing up disk space on Cassandra 1.1.5 with Size-Tiered
compaction.
“ Having so much data on each node is a potential bad day.”
Is this discussed somewhere on the Cassandra documentation (limits, practices
etc)? We are also trying to load up quite a lot of data
Basically we were successful on two of the nodes. They both took ~2 days and
11 hours to complete and at the end we saw one very large file ~900GB and the
rest much smaller (the overall size decreased). This is what we expected!
I would recommend having up to 300MB to 400MB per node on a
Hi Alexandru,
We are running a 3 node Cassandra 1.1.5 cluster with a 3TB Raid 0 disk per
node for the data dir and separate disk for the commitlog, 12 cores, 24 GB
RAM
I think you should tune your architecture in a very different way. From
what I know having too much data on one node is bad, not
From what I know having too much data on one node is bad, not really sure
why, but I think that performance will go down due to the size of indexes
and bloom filters (I may be wrong on the reasons but I'm quite sure you can't
store too much data per node).
If you have many hundreds of
11 matches
Mail list logo
