You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Matthew Johnson <ma...@algomi.com> on 2015/05/26 15:24:53 UTC
Start with single node, move to 3-node cluster
Hi gurus,
We have ordered some hardware for a 3-node cluster, but its ETA is 6 to 8
weeks. In the meantime, I have been lent a single server that I can use. I
am wondering what the best way is to set up my single node (SN), so I can
then move to the 3-node cluster (3N) when the hardware arrives.
Do I:
1. Create my keyspaces on SN with RF=1, and when 3N is up and running
migrate all the data manually (either through Spark, dump-and-load, or
write a small script)?
2. Create my keyspaces on SN with RF=3, bootstrap the 3N nodes into a
4-node cluster when they’re ready, then remove SN from the cluster?
3. Use SN as normal, and when 3N hardware arrives, physically move
the data folder and commit log folder onto one of the nodes in 3N and start
it up as a seed?
4. Any other recommended solutions?
I’m not even sure what the impact would be of running a single node with
RF=3 – would this even work?
Any ideas would be much appreciated.
Thanks!
Matthew
Re: Start with single node, move to 3-node cluster
Posted by Ajaya Agrawal <aj...@gmail.com>.
If it is necessary to start the cluster now then create 3 vms in one
machine and start up the cluster. The performance would not be as good as 3
individual nodes, but it will do the job for time being. Later when more
nodes arrive start decommissioning vms one by one and add the physical
nodes. Decommissioning the last vm would be a bit tricky.
Otherwise just get some operational experience by creating C* clusters with
vms until the real machines arrive.
Cheers,
Ajaya
On Thu, May 28, 2015 at 12:25 PM, Jason Wee <pe...@gmail.com> wrote:
> hmm..i supposed you start with rf = 1 and then when 3n arrived, just add
> into the cluster and later decomission this one node?
> http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_remove_node_t.html
>
> hth
>
> jason
>
> On Tue, May 26, 2015 at 10:02 PM, Matthew Johnson <matt.johnson@algomi.com
> > wrote:
>
>> Hi Jason,
>>
>>
>>
>> When the 3N cluster is up and running, I need to get the data from SN
>> into the 3N cluster and then give the SN server back. So I need to keep the
>> data, but on completely new servers – just trying to work out what the best
>> way of doing that is. The volume of data that needs migrating won’t be
>> huge, probably about 30G, but it is data that I definitely need to keep
>> (for historical analysis, audit etc).
>>
>>
>>
>> Thanks!
>>
>> Matthew
>>
>>
>>
>>
>>
>>
>>
>> *From:* Jason Wee [mailto:peichieh@gmail.com]
>> *Sent:* 26 May 2015 14:38
>> *To:* user@cassandra.apache.org
>> *Subject:* Re: Start with single node, move to 3-node cluster
>>
>>
>>
>> will you add this lent one node into the 3N to form a cluster? but really
>> , if you are just started, you could use this one node for your learning by
>> installing multiple instances for experiments or development purposes only.
>> imho, in the long run, this proove to be very valuable, as least for me.
>>
>>
>>
>> with this single node, you can easily simulate like c* upgrade. for
>> instance, c* right now is at 2.1.5, when 2.2 went stable, you can test
>> using your multiple instances on this single node to simulate your
>> production environment safely.
>>
>>
>>
>> hth
>>
>>
>>
>> jason
>>
>>
>>
>> On Tue, May 26, 2015 at 9:24 PM, Matthew Johnson <ma...@algomi.com>
>> wrote:
>>
>> Hi gurus,
>>
>>
>>
>> We have ordered some hardware for a 3-node cluster, but its ETA is 6 to 8
>> weeks. In the meantime, I have been lent a single server that I can use. I
>> am wondering what the best way is to set up my single node (SN), so I can
>> then move to the 3-node cluster (3N) when the hardware arrives.
>>
>>
>>
>> Do I:
>>
>>
>>
>> 1. Create my keyspaces on SN with RF=1, and when 3N is up and
>> running migrate all the data manually (either through Spark, dump-and-load,
>> or write a small script)?
>>
>> 2. Create my keyspaces on SN with RF=3, bootstrap the 3N nodes
>> into a 4-node cluster when they’re ready, then remove SN from the cluster?
>>
>> 3. Use SN as normal, and when 3N hardware arrives, physically move
>> the data folder and commit log folder onto one of the nodes in 3N and start
>> it up as a seed?
>>
>> 4. Any other recommended solutions?
>>
>>
>>
>> I’m not even sure what the impact would be of running a single node with
>> RF=3 – would this even work?
>>
>>
>>
>> Any ideas would be much appreciated.
>>
>>
>>
>> Thanks!
>>
>> Matthew
>>
>>
>>
>>
>>
>
>
Re: Start with single node, move to 3-node cluster
Posted by Jason Wee <pe...@gmail.com>.
hmm..i supposed you start with rf = 1 and then when 3n arrived, just add
into the cluster and later decomission this one node?
http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_remove_node_t.html
hth
jason
On Tue, May 26, 2015 at 10:02 PM, Matthew Johnson <ma...@algomi.com>
wrote:
> Hi Jason,
>
>
>
> When the 3N cluster is up and running, I need to get the data from SN into
> the 3N cluster and then give the SN server back. So I need to keep the
> data, but on completely new servers – just trying to work out what the best
> way of doing that is. The volume of data that needs migrating won’t be
> huge, probably about 30G, but it is data that I definitely need to keep
> (for historical analysis, audit etc).
>
>
>
> Thanks!
>
> Matthew
>
>
>
>
>
>
>
> *From:* Jason Wee [mailto:peichieh@gmail.com]
> *Sent:* 26 May 2015 14:38
> *To:* user@cassandra.apache.org
> *Subject:* Re: Start with single node, move to 3-node cluster
>
>
>
> will you add this lent one node into the 3N to form a cluster? but really
> , if you are just started, you could use this one node for your learning by
> installing multiple instances for experiments or development purposes only.
> imho, in the long run, this proove to be very valuable, as least for me.
>
>
>
> with this single node, you can easily simulate like c* upgrade. for
> instance, c* right now is at 2.1.5, when 2.2 went stable, you can test
> using your multiple instances on this single node to simulate your
> production environment safely.
>
>
>
> hth
>
>
>
> jason
>
>
>
> On Tue, May 26, 2015 at 9:24 PM, Matthew Johnson <ma...@algomi.com>
> wrote:
>
> Hi gurus,
>
>
>
> We have ordered some hardware for a 3-node cluster, but its ETA is 6 to 8
> weeks. In the meantime, I have been lent a single server that I can use. I
> am wondering what the best way is to set up my single node (SN), so I can
> then move to the 3-node cluster (3N) when the hardware arrives.
>
>
>
> Do I:
>
>
>
> 1. Create my keyspaces on SN with RF=1, and when 3N is up and
> running migrate all the data manually (either through Spark, dump-and-load,
> or write a small script)?
>
> 2. Create my keyspaces on SN with RF=3, bootstrap the 3N nodes into
> a 4-node cluster when they’re ready, then remove SN from the cluster?
>
> 3. Use SN as normal, and when 3N hardware arrives, physically move
> the data folder and commit log folder onto one of the nodes in 3N and start
> it up as a seed?
>
> 4. Any other recommended solutions?
>
>
>
> I’m not even sure what the impact would be of running a single node with
> RF=3 – would this even work?
>
>
>
> Any ideas would be much appreciated.
>
>
>
> Thanks!
>
> Matthew
>
>
>
>
>
RE: Start with single node, move to 3-node cluster
Posted by Matthew Johnson <ma...@algomi.com>.
Hi Jason,
When the 3N cluster is up and running, I need to get the data from SN into
the 3N cluster and then give the SN server back. So I need to keep the
data, but on completely new servers – just trying to work out what the best
way of doing that is. The volume of data that needs migrating won’t be
huge, probably about 30G, but it is data that I definitely need to keep
(for historical analysis, audit etc).
Thanks!
Matthew
*From:* Jason Wee [mailto:peichieh@gmail.com]
*Sent:* 26 May 2015 14:38
*To:* user@cassandra.apache.org
*Subject:* Re: Start with single node, move to 3-node cluster
will you add this lent one node into the 3N to form a cluster? but really ,
if you are just started, you could use this one node for your learning by
installing multiple instances for experiments or development purposes only.
imho, in the long run, this proove to be very valuable, as least for me.
with this single node, you can easily simulate like c* upgrade. for
instance, c* right now is at 2.1.5, when 2.2 went stable, you can test
using your multiple instances on this single node to simulate your
production environment safely.
hth
jason
On Tue, May 26, 2015 at 9:24 PM, Matthew Johnson <ma...@algomi.com>
wrote:
Hi gurus,
We have ordered some hardware for a 3-node cluster, but its ETA is 6 to 8
weeks. In the meantime, I have been lent a single server that I can use. I
am wondering what the best way is to set up my single node (SN), so I can
then move to the 3-node cluster (3N) when the hardware arrives.
Do I:
1. Create my keyspaces on SN with RF=1, and when 3N is up and running
migrate all the data manually (either through Spark, dump-and-load, or
write a small script)?
2. Create my keyspaces on SN with RF=3, bootstrap the 3N nodes into a
4-node cluster when they’re ready, then remove SN from the cluster?
3. Use SN as normal, and when 3N hardware arrives, physically move
the data folder and commit log folder onto one of the nodes in 3N and start
it up as a seed?
4. Any other recommended solutions?
I’m not even sure what the impact would be of running a single node with
RF=3 – would this even work?
Any ideas would be much appreciated.
Thanks!
Matthew
Re: Start with single node, move to 3-node cluster
Posted by Jason Wee <pe...@gmail.com>.
will you add this lent one node into the 3N to form a cluster? but really ,
if you are just started, you could use this one node for your learning by
installing multiple instances for experiments or development purposes only.
imho, in the long run, this proove to be very valuable, as least for me.
with this single node, you can easily simulate like c* upgrade. for
instance, c* right now is at 2.1.5, when 2.2 went stable, you can test
using your multiple instances on this single node to simulate your
production environment safely.
hth
jason
On Tue, May 26, 2015 at 9:24 PM, Matthew Johnson <ma...@algomi.com>
wrote:
> Hi gurus,
>
>
>
> We have ordered some hardware for a 3-node cluster, but its ETA is 6 to 8
> weeks. In the meantime, I have been lent a single server that I can use. I
> am wondering what the best way is to set up my single node (SN), so I can
> then move to the 3-node cluster (3N) when the hardware arrives.
>
>
>
> Do I:
>
>
>
> 1. Create my keyspaces on SN with RF=1, and when 3N is up and
> running migrate all the data manually (either through Spark, dump-and-load,
> or write a small script)?
>
> 2. Create my keyspaces on SN with RF=3, bootstrap the 3N nodes into
> a 4-node cluster when they’re ready, then remove SN from the cluster?
>
> 3. Use SN as normal, and when 3N hardware arrives, physically move
> the data folder and commit log folder onto one of the nodes in 3N and start
> it up as a seed?
>
> 4. Any other recommended solutions?
>
>
>
> I’m not even sure what the impact would be of running a single node with
> RF=3 – would this even work?
>
>
>
> Any ideas would be much appreciated.
>
>
>
> Thanks!
>
> Matthew
>
>
>