If u ask conceptually, it is possible but not recommended.
If u really want to do it use the initial token setting and provide the
broad range to the nodes where u want more data. But u need to understand
about the replication factor consideration, if u keep rf as 3 on a 3 node
cluster that means
Hi,
Thanks all for your valuable suggestion.
Thanks and Regards
A.SathishKumar
On Sat, Nov 12, 2016 at 2:59 PM, Ben Bromhead wrote:
> +1 w/ Benjamin.
>
> However if you wish to make use of spare hardware capacity, look to
> something like mesos DC/OS or kubernetes. You
+1 w/ Benjamin.
However if you wish to make use of spare hardware capacity, look to
something like mesos DC/OS or kubernetes. You can run multiple services
across a fleet of hardware, but provision equal resources to Cassandra and
have somewhat reliable hardware sharing mechanisms.
On Sat, 12
Agreed w/ Benjamin. Trying to diagnose issues in prod will be a nightmare.
Keep your DB servers homogeneous.
> On Nov 12, 2016, at 1:52 PM, Benjamin Roth wrote:
>
> 1. From a 15 year experience of running distributed Services: dont Mix
> Services on machines if
1. From a 15 year experience of running distributed Services: dont Mix
Services on machines if you don't have to. Dedicate each server to a single
task if you can afford it. It is easier to manage and reduces risks in case
of overload or failure
2. You can assign a different number of tokens for
Hi,
We are planning to install 3 node cluster in production environment. Is it
possible to provide weightage or priority to the nodes in cluster.
Eg., We want more more records to be written to first 2 nodes and less to
the 3rd node. We are thinking of this approach because we want to install