So you mean this part doesn't need more testing ? This will work for sure ?
Did you already did it yourself ?
Always test.
But if you only had one AZ then all nodes will be in one Rack, so the NTS will
not behave differently.
C* will be able to reach the LOCAL_QUORUM everywhere, won't it
If you are only using one Available Zone per region then you have only one
rack per DC and the NetworkTopologyStrategy will do the right thing.
So you mean this part doesn't need more testing ? This will work for sure ?
Did you already did it yourself ?
Because you are going to replicate your
Hi,these advice are very welcome.
@Dane, about the rack awareness, we use only one rack per DC, so I guess
using EC2MultiRegionSnitch will do just fine and it doesn't need any
configuration. Does it seem right to you. If we are someday interested on
multi racks I will make sure to use them
You are advising me to test it, what would be a good way of testing it (I can
use AWS EC2 instances if needed) ?
If you are only using one Available Zone per region then you have only one rack
per DC and the NetworkTopologyStrategy will do the right thing.
Why ? I mean we have maybe only 5%
On Thu, Apr 18, 2013 at 7:41 AM, Alain RODRIGUEZ arodr...@gmail.com wrote:
I am wondering about the process to grow from one data center to a few of
them. First thing is we use EC2Snitch for now. So I guess we have to switch
to Ec2MultiRegionSnitch.
c/ I am using the SimpleStrategy. Is it
of the 6 eu-west existing nodes
- Ec2Snitch to Ec2MultiRegionSnitch
- uncomment the broadcast_address and set the public ip of the node
- let the private ip as defined right now the listen_address
- switch seeds from private to public IP
2/ Rolling restart
- nodetool
Hi,
As of Nov. 9, 2011 Amazon added us-west-2 (US West Oregon) region:
http://aws.typepad.com/aws/2011/11/now-open-us-west-portland-region.html
In looking at the EC2Snitch code (in the 0.8.x and 1.0.x branches), I see
it determining which data center (which I think is supposed to be
equivalent
