Re: Creating a copy of a C* cluster

[Erick Ramirez]

Fay, it's normal to need to increase the max heap for sstableloader if you
have large data sets. Cheers!

On Wed, Aug 16, 2017 at 1:18 AM, Fay Hou [Storage Service] ­ <
fay...@coupang.com> wrote:

> We do snapshot and sstableloader. with sstableloader, it is ok to have
> different configuration of the "stand by" cluster (i.e. number of the
> nodes).
> however, there is a issue we ran into with the sstableloader 
> (java.lang.OutOfMemoryError:
> GC overhead limit exceeded)
>  https://issues.apache.org/jira/browse/CASSANDRA-7385
>
> Thanks,
> Fay
>
> On Tue, Aug 15, 2017 at 12:58 AM, Erick Ramirez 
> wrote:
>
>> A slight variation to Ben Slater's idea is to build the second cluster
>> like-for-like and assigning the same tokens used by the original nodes. If
>> you restore the data onto the equivalent nodes with the same tokens, the
>> data will be accessible as normal. Cheers!
>>
>> On Tue, Aug 8, 2017 at 7:08 AM, Robert Wille  wrote:
>>
>>> We need to make a copy of a cluster. We’re going to do some testing
>>> against the copy and then discard it. What’s the best way of doing that? I
>>> created another datacenter, and then have tried to divorce it from the
>>> original datacenter, but have had troubles doing so.
>>>
>>> Suggestions?
>>>
>>> Thanks in advance
>>>
>>> Robert
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>>
>>
>>
>

Re: Creating a copy of a C* cluster

[Fay Hou [Storage Service] ­]

We do snapshot and sstableloader. with sstableloader, it is ok to have
different configuration of the "stand by" cluster (i.e. number of the
nodes).
however, there is a issue we ran into with the sstableloader
(java.lang.OutOfMemoryError:
GC overhead limit exceeded)
 https://issues.apache.org/jira/browse/CASSANDRA-7385

Thanks,
Fay
On Tue, Aug 15, 2017 at 12:58 AM, Erick Ramirez 
wrote:

> A slight variation to Ben Slater's idea is to build the second cluster
> like-for-like and assigning the same tokens used by the original nodes. If
> you restore the data onto the equivalent nodes with the same tokens, the
> data will be accessible as normal. Cheers!
>
> On Tue, Aug 8, 2017 at 7:08 AM, Robert Wille  wrote:
>
>> We need to make a copy of a cluster. We’re going to do some testing
>> against the copy and then discard it. What’s the best way of doing that? I
>> created another datacenter, and then have tried to divorce it from the
>> original datacenter, but have had troubles doing so.
>>
>> Suggestions?
>>
>> Thanks in advance
>>
>> Robert
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>
>
>

Re: Creating a copy of a C* cluster

[Erick Ramirez]

A slight variation to Ben Slater's idea is to build the second cluster
like-for-like and assigning the same tokens used by the original nodes. If
you restore the data onto the equivalent nodes with the same tokens, the
data will be accessible as normal. Cheers!

On Tue, Aug 8, 2017 at 7:08 AM, Robert Wille  wrote:

> We need to make a copy of a cluster. We’re going to do some testing
> against the copy and then discard it. What’s the best way of doing that? I
> created another datacenter, and then have tried to divorce it from the
> original datacenter, but have had troubles doing so.
>
> Suggestions?
>
> Thanks in advance
>
> Robert
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>

Re: Creating a copy of a C* cluster

[kurt greaves]

The most effective way to "divorce" it is to remove connectivity between
the datacentres. I would put in place firewall rules between the DC's to
stop them from communicating, and then rolling restart one of the DC's. You
should be left with 2 datacentres that see each other as down, and on each
one you can then go ahead and remove the opposite DC from replication, and
then remove the nodes from the other DC (via nodetool removenode). Before
changing RF or removing nodes make completely sure that there is *no way* for
the DC's to communicate.​

Re: Creating a copy of a C* cluster

[Ben Slater]

For minimum disruption to your production cluster, restoring from backups
is probably the best option. However, there is no reason adding a DC,
building and then splitting shouldn’t work if done correct.

Cheers
Ben

On Tue, 8 Aug 2017 at 07:11 Robert Wille  wrote:

> We need to make a copy of a cluster. We’re going to do some testing
> against the copy and then discard it. What’s the best way of doing that? I
> created another datacenter, and then have tried to divorce it from the
> original datacenter, but have had troubles doing so.
>
> Suggestions?
>
> Thanks in advance
>
> Robert
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
-- 


*Ben Slater*

*Chief Product Officer *

   


Read our latest technical blog posts here
.

This email has been sent on behalf of Instaclustr Pty. Limited (Australia)
and Instaclustr Inc (USA).

This email and any attachments may contain confidential and legally
privileged information.  If you are not the intended recipient, do not copy
or disclose its content, but please reply to this email immediately and
highlight the error to the sender and then immediately delete the message.

Creating a copy of a C* cluster

[Robert Wille]

We need to make a copy of a cluster. We’re going to do some testing against the 
copy and then discard it. What’s the best way of doing that? I created another 
datacenter, and then have tried to divorce it from the original datacenter, but 
have had troubles doing so.

Suggestions?

Thanks in advance

Robert


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org