Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: <CAAafH9TG4KrEqa-sLA8Pso5heBA+9-5Vmym0sumSVUgTs9x7ag@mail.gmail.com>
References: <CAPw3+DiruXkUow9GueNcCuVnROm3tqB80YDJToPPoU67n9eJrg@mail.gmail.com>
 <CAAafH9TG4KrEqa-sLA8Pso5heBA+9-5Vmym0sumSVUgTs9x7ag@mail.gmail.com>
From: Dikang Gu <dikang85@gmail.com>
Date: Sun, 11 Sep 2016 23:27:16 -0700
Message-ID: <CAPw3+DgP+8HH6TKqX6hUSGvyWvsRE7hJcR84jRyaoaxMiChQ4A@mail.gmail.com>
Subject: Re: Can we change the number of vnodes on existing nodes?
To: dev@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a113ce134991c98053c49974f
archived-at: Mon, 12 Sep 2016 06:27:53 -0000

--001a113ce134991c98053c49974f
Content-Type: text/plain; charset=UTF-8

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 PM, Brandon Williams <driftx@gmail.com> wrote:

> I am curious exactly what gossip issues you are encountering.
>
> On Fri, Sep 9, 2016 at 7:45 PM, Dikang Gu <dikang85@gmail.com> 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 existing nodes, is
> > there any reason that we can not support it? It should not be too
> different
> > from moving the node with one single token, right?
> >
> > Thanks
> > Dikang
> >
>


-- 
Dikang

--001a113ce134991c98053c49974f--