Re: Can we change the number of vnodes on existing nodes?

2016-09-12 Thread Dikang Gu
Thanks for the suggestions! I may consider the new dc solution, although it would involve significant operational work in our scale. For gossip issue, like: https://issues.apache.org/jira/browse/CASSANDRA-11709, https://issues.apache.org/jira/browse/CASSANDRA-11740 On Fri, Sep 9, 2016 at 9:55

Re: Can we change the number of vnodes on existing nodes?

2016-09-09 Thread Brandon Williams
I am curious exactly what gossip issues you are encountering. On Fri, Sep 9, 2016 at 7:45 PM, Dikang Gu wrote: > Hi, > > We have some big cluster (500+ nodes), they have 256 vnodes on physical > host, which is causing a lot of problems to us, especially make the gossip > to

Re: Can we change the number of vnodes on existing nodes?

2016-09-09 Thread Nate McCall
The "easiest" (in quotes given the size of that cluster) approach is to add a new datacenter with shiny new nodes and configured for single token. Once the 'add' is complete, de-commission the old one. This approach of evacuating to a new DC is pretty safe. The only downside is the temporary 2x

Re: Can we change the number of vnodes on existing nodes?

2016-09-09 Thread Jeff Jirsa
On 9/9/16, 5:45 PM, "Dikang Gu" wrote: >Hi, > >We have some big cluster (500+ nodes), they have 256 vnodes on physical >host, which is causing a lot of problems to us, especially make the gossip >to be in-efficient. > >There seems no way to change the number of vnodes on

Can we change the number of vnodes on existing nodes?

2016-09-09 Thread Dikang Gu
Hi, We have some big cluster (500+ nodes), they have 256 vnodes on physical host, which is causing a lot of problems to us, especially make the gossip to be in-efficient. There seems no way to change the number of vnodes on existing nodes, is there any reason that we can not support it? It