Dan,
AFAIK, AZ gives you infrastructure redundancy but not necessarily
geographical dispersion. Regions are meant for that (as well as other
characteristics).
An interesting blog on this topic
http://alestic.com/2009/07/ec2-availability-zones
Cheers
On 4/4/10 Sun Apr 4, 10, "Dan Di Spalt
Not guaranteed within the same region.
On Sun, Apr 4, 2010 at 6:48 PM, Dan Di Spaltro wrote:
> A little off-topic, but is an availability zone in a separate physical
> datacenter?
>
On 2010-04-04, at 10:18 PM, Masood Mortazavi wrote:
>
> (My question remains. I'm interested in seed configuration practice/recipe
> when deploying on AWS. In the scenario, assume Cassandra sits behind some
> other part of the service -- say, web container -- that are then exposed
> publicly. C
See here:
http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/index.html?concepts-regions-availability-zones.html
(My question remains. I'm interested in seed configuration practice/recipe
when deploying on AWS. In the scenario, assume Cassandra sits behind some
other part of the service --
A little off-topic, but is an availability zone in a separate physical
datacenter?
On Sat, Apr 3, 2010 at 5:08 PM, Benjamin Black wrote:
> Right, you determine AZ by looking at the metadata. us-east-1a is a
> different AZ from us-east-1b. You can't infer anything beyond that,
> either with the
Pluggable placement: that is cool. It wasn't something that was obvious to me
that was available from the documentation I read. I thought maybe the the
rackaware and rackunaware were hard coded in somewhere. I'm not a java
developer so I haven't looked at the code much. That said I'll take a lo
On Sat, Apr 3, 2010 at 8:23 PM, Mike Gallamore
wrote:
>>
> I didn't mean a real time determination, more of if the nodes aren't
> identical. For example if you have a cluster made up of a bunch of EC2 light
> instances and decide to add a large instance, it would be nice if the new
> node would
Hi Benjamin,
Thanks for the reply.
On 2010-04-03, at 8:12 PM, Benjamin Black wrote:
> On Sat, Apr 3, 2010 at 3:41 PM, Mike Gallamore
> wrote:
>>
>> Useful things that nodes could advertise:
>>
>> data-centre they are in,
>
> This is what the snitches do.
Cool.
>
>> performance info: mem, CPU
On Sat, Apr 3, 2010 at 3:41 PM, Mike Gallamore
wrote:
>
> Useful things that nodes could advertise:
>
> data-centre they are in,
This is what the snitches do.
> performance info: mem, CPU etc (these could be used to more intelligently
> decide how to partition the data that the new node gets fo
Right, you determine AZ by looking at the metadata. us-east-1a is a
different AZ from us-east-1b. You can't infer anything beyond that,
either with the AWS API or guesses about IP addressing. My EC2 snitch
recipe builds a config file for the property snitch that treats AZs
like racks (just break
Hi everyone,
At my work we are in the early stages of moving our data which lives on EC2
machines from a Flare/memcache system to Cassandra so your chat has been
interesting to me.
I realize that this might complicate things and make things less "simple" but
would it be useful for the nodes th
On Apr 3, 2010, at 2:54 PM, Benjamin Black wrote:
> I'm pretty familiar with EC2, hence the question. I don't believe any
> patches are required to do these things. Regardless, as I noted in
> that ticket, you definitely do NOT need AWS credentials to determine
> your availability zone. It is
I'm pretty familiar with EC2, hence the question. I don't believe any
patches are required to do these things. Regardless, as I noted in
that ticket, you definitely do NOT need AWS credentials to determine
your availability zone. It is available through the metadata web
server for each instance
On Apr 3, 2010, at 1:53 PM, Benjamin Black wrote:
> What specific features are you looking for to operate on EC2?
It seemed people weren't looking for features, but tools to help with the
management. The two things we've created that people might be interested in are:
1. An EC2-specific rack-a
What specific features are you looking for to operate on EC2?
b
On Sat, Apr 3, 2010 at 1:37 PM, Lenin Gali wrote:
> We are looking to take advantage of this as Well. Please let us know when it
> is ready.
>
> Lenin
>
> On Sat, Apr 3, 2010 at 11:32 AM, Peter Chang wrote:
>>
>> Woot. Ver much lo
We are looking to take advantage of this as Well. Please let us know when it
is ready.
Lenin
On Sat, Apr 3, 2010 at 11:32 AM, Peter Chang wrote:
> Woot. Ver much looking forward to this stuff Joe.
>
>
> On Sat, Apr 3, 2010 at 10:14 AM, Joe Stump wrote:
>
>>
>> On Apr 2, 2010, at 4:49 PM, Masoo
Woot. Ver much looking forward to this stuff Joe.
On Sat, Apr 3, 2010 at 10:14 AM, Joe Stump wrote:
>
> On Apr 2, 2010, at 4:49 PM, Masood Mortazavi wrote:
>
> > Is there a ready recipe for deploying a Cassandra cluster in AWS? ...
> (Seeds need some "fixed" IP addresses.)
>
> We have a lot of c
On Apr 2, 2010, at 4:49 PM, Masood Mortazavi wrote:
> Is there a ready recipe for deploying a Cassandra cluster in AWS? ... (Seeds
> need some "fixed" IP addresses.)
We have a lot of code around this that we're trying to get released. We have a
rack aware strategy for cross-AZ clusters. We als
http://github.com/b/cookbooks/tree/master/cassandra/
On Fri, Apr 2, 2010 at 4:49 PM, Masood Mortazavi
wrote:
>
> Is there a ready recipe for deploying a Cassandra cluster in AWS? ... (Seeds
> need some "fixed" IP addresses.)
>
> Regards,
> - m.
>
>
19 matches
Mail list logo
