t understand the “node density”
> point.
>
>
>
> Charu
>
>
>
> *From:* Rahul Singh
> *Reply-To:* "user@cassandra.apache.org"
> *Date:* Monday, February 19, 2018 at 12:32 PM
> *To:* "user@cassandra.apache.org"
> *Subject:* Re: Right sizing
>
Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Monday, February 19, 2018 at 12:32 PM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Re: Right sizing Cassandra data nodes
1. I would keep opscenter on different
om: Rahul Singh
> Reply-To: "user@cassandra.apache.org"
> Date: Monday, February 19, 2018 at 12:32 PM
> To: "user@cassandra.apache.org"
> Subject: Re: Right sizing Cassandra data nodes
>
> 1. I would keep opscenter on different cluster. Why unnecessarily put
Thanks for the response Rahul. I did not understand the “node density” point.
Charu
From: Rahul Singh
Reply-To: "user@cassandra.apache.org"
Date: Monday, February 19, 2018 at 12:32 PM
To: "user@cassandra.apache.org"
Subject: Re: Right sizing Cassandra data nodes
1. I wou
1. I would keep opscenter on different cluster. Why unnecessarily put traffic
and computing for opscenter data on a real business data cluster?
2. Don’t put more than 1-2 TB per node. Maybe 3TB. Node density as it increases
creates more replication, read repairs , etc and memory usage for doing t
Hi All,
Looking for some insight into how application data archive and purge is carried
out for C* database. Are there standard guidelines on calculating the amount of
space that can be used for storing data in a specific node.
Some pointers that I got while researching are;
- Alloca
