On Sat, Apr 3, 2010 at 8:23 PM, Mike Gallamore
mike.e.gallam...@googlemail.com 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
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.
Woot. Ver much looking forward to this stuff Joe.
On Sat, Apr 3, 2010 at 10:14 AM, Joe Stump j...@joestump.net 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
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
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 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
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
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
