On Mon, Mar 26, 2012 at 3:31 PM, Deno Vichas > but what if i already
have a bunch (8g per node) data that i need and i
> don't have a way to re-create it.
Note that the below may have unintended consequences if using Counter
column families. It actually can be done with the cluster running,
below
I've switched from SS to NTS on 1.0.x on a single-az cluster with RF3 (which
obviously created a single-dc, single-rack NTS cluster). Worked without a
hitch. Also switched from SimpleSnitch to Ec2Snitch on-the-fly. I had about
12GB of data per node.
Of course, your mileage may vary, so while I
I'm kind of guessing here because it's not something I've done before.
Obviously test things first…
The NTS with a single DC and a single Rack will place data in the same location
as the Simple Strategy. You *should* be able to change the replication strategy
from, say, SS with RF 3 to NTS with
On 3/26/2012 2:15 PM, aaron morton wrote:
- can i migrate the replication strategy one node at a time or do i need to
shut to the whole cluster to do this?
Just use the NTS from the start.
but what if i already have a bunch (8g per node) data that i need and i
don't have a way to re-create it.
> (rep factor 3, simple)
if this means you are using the SimpleStrategy I would recommend using the
NetworkTopologyStrategy.
> - what is the min and recommended number of nodes to use in multiple region
> cluster. we only have a single app server right now.
It depends on how exciting you want
all,
we just about ready to push our app live and just have some cassandra
tuning left. i've been currently running a 4 node (rep factor 3,
simple) in EC2 using the datastax AMIs (thanks datastax). so after
reading through a bunch of docs i have a few questions.
- what is the min and reco
