cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juan Manuel Formoso <>
Subject Re: I don't understand shuffle progress
Date Wed, 18 Sep 2013 15:28:44 GMT
Awesome, thanks!

A few final questions:
1) Can I change the Snitch in the live source cluster? I'm using
SimpleSnitch, I'd change it to GossipingPropertyFileSnitch (in preparation
for changing the replication strategy when the new cluster is up and
2) Can I have different Partitioners on the 2 clusters? I have
RandomPartitioner in the current one, I'd like to use Murmur on the new one
(it will be empty at first). Are partitioners only required to be the same
in the same cluster or also across clusters in different DCs?
3) Will I be able to remove the old dc from the cluster when I finish

Thanks again!

On Wed, Sep 18, 2013 at 11:41 AM, Chris Burroughs <
> wrote:

> webhelp/index.html#cassandra/**operations/ops_add_dc_to_**cluster_t.html<>
> This is a basic outline.
> On 09/18/2013 10:32 AM, Juan Manuel Formoso wrote:
>> I really like this idea. I can create a new cluster and have it replicate
>> the old one, after it finishes I can remove the original.
>> Any good resource that explains how to add a new datacenter to a live
>> single dc cluster that anybody can recommend?
>> On Wed, Sep 18, 2013 at 9:58 AM, Chris Burroughs
>> <>**wrote:
>>  On 09/17/2013 09:41 PM, Paulo Motta wrote:
>>>  So you're saying the only feasible way of enabling VNodes on an upgraded
>>>> C*
>>>> 1.2 is by doing fork writes to a brand new cluster + bulk load of
>>>> sstables
>>>> from the old cluster? Or is it possible to succeed on shuffling, even if
>>>> that means waiting some weeks for the shuffle to complete?
>>> In a multi "DC" cluster situation you *should* be able to bring up a new
>>> DC with vnodes, bootstrap it, and then decommission the old cluster.

*Juan Manuel Formoso
*Senior Geek

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message