n supports
disabling/re-enabling (or restarting the cluster) and resuming from the
last position? Or does it start over?
--
*Juan Manuel Formoso
*Senior Geek
http://twitter.com/juanformoso
http://seniorgeek.com.ar
LLAP
body can suggest?
On Tuesday, September 17, 2013, Robert Coli wrote:
> On Tue, Sep 17, 2013 at 12:13 PM, Juan Manuel Formoso
>
> >wrote:
>
> > I am running shuffle on a cluster after upgrading to 1.2.X, and I don't
> > understand how to check progress.
> >
data from one disk to the other, remove
the configuration for the second disk, and re-start cassandra?
I assume files will not have the same name and thus not be overwritten, is
this the case? Does it pick it up just like that?
Thanks
--
*Juan Manuel Formoso
*Senior Geek
http://twitter.com/juanfo
for the shuffle to complete?
>
>
> 2013/9/17 Robert Coli
>
> > On Tue, Sep 17, 2013 at 4:00 PM, Juan Manuel Formoso > >wrote:
> >
> > > Any better alternatives than creating a small application that reads
> from
> > > one cluster and inserts in
cceed 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.
>
--
a/1.2/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,
tion strategy is
not referencing it.
However, I don't want to see them forever listed there. Is there a way to
manually remove them from the "known replicas list" or wherever they are
stored?
--
*Juan Manuel Formoso
*Senior Geek
http://twitter.com/juanformoso
http://seniorgeek.com.ar
LLAP
