ok, I will test again and let you know.
SD - to secure data stream between EC2 regions, can we not just setup
a VPN in EC2 with this patch ?
On Wed, Mar 23, 2011 at 8:50 PM, Milind Parikh wrote:
> My nodetool repair does not hang. That's why I'm curious.
>
> /***
> sent from
My nodetool repair does not hang. That's why I'm curious.
/***
sent from my android...please pardon occasional typos as I respond @ the
speed of thought
/
On Mar 23, 2011 2:54 PM, "A J" wrote:
7000 and 9160 are accessible. Don't think I need other por
7000 and 9160 are accessible. Don't think I need other ports for basic
setup , right ?
If anyone coud get 'nodetool repair' working with this patch (across
regions), let me know. It may be I am doing something wrong.
On Wed, Mar 23, 2011 at 1:08 AM, Milind Parikh wrote:
> @aj
> are you sure that
@aj
are you sure that all ports are accessible from all node?
@sasha
I think that being able to have the semantics of address aNAT address can
emable security from different perspective. Describing an overlay nw will
take long hete. But that may solve your security concerns over the internet.
/*
there are some other knock on issues too. the SSL work that has been
done would also have to be changed ...
-sd
On Tue, Mar 22, 2011 at 6:58 PM, A J wrote:
> Milind,
> Among the limitation you might want to add that 'nodetool repair' does
> not work with this patch.
> I tried several times and
Milind,
Among the limitation you might want to add that 'nodetool repair' does
not work with this patch.
I tried several times and the repair hangs.
When I run it directly on the trunk of 0.7.4 (without the patch) it
completes successfully within reasonable time.
Thanks.
On Tue, Mar 22, 2011 at 1
Never mind - I had thought it was more generalizable but since it's just going
against the public IP between regions, that's not going to be something that
makes it into trunk. I had just wanted to see if there was a way that it could
be done, but it sounds like since amazon doesn't provide dec
Milind,
Thank you for attaching the patch here, but it would be really nice if you
could create a jira account so you could participate in the discussion on the
ticket and put the patch on there - that is the way people license their
contributions with the apache 2 license. You just need to cr
Thanks Milind for sharing!
As Sasha already asked, ec2 sends data across regions over the
internet without any encryption. So you may consider to tunnel the traffic
thru ssh.
I don't know how to do that with cassandra. Any?
Regards, mike
On Tue, Mar 22, 2011 at 5:29 AM, Milind Parikh wrote:
>
Patch is attached... I don't have access to Jira.
A cautionery note: This is NOT a general solution and is not intended as
such. It could be included as a part of larger patch. I will explain in the
limitation sections about why it is not a general solution; as I find time.
Regards
Milind
On Mon
Sorry if I was presumptuous earlier. I created a ticket so that the patch
could be submitted and reviewed - that is if it can be generalized so that it
works across regions and doesn't adversely affect the common case.
https://issues.apache.org/jira/browse/CASSANDRA-2362
On Mar 21, 2011, at 10:
I talked to Matt Dennis in the channel about it and I think everyone would like
to make sure that cassandra works great across multiple regions. He sounded
like he didn't know why it wouldn't work after having looked at the patches. I
would like to try it both ways - with and without the patch
Hi Milind,
Great work here. Can you provide the patch against the 2 files?
Perhaps there's some way to incorporate it into the trunk of cassandra so
that this is feasible (in a future release) without patching the source
code.
Dave Viner
On Mon, Mar 21, 2011 at 9:41 AM, A J wrote:
> Thanks
Thanks for sharing the document, Milind !
Followed the instructions and it worked for me.
On Mon, Mar 21, 2011 at 5:01 AM, Milind Parikh wrote:
> Here's the document on Cassandra (0.7.4) across EC2 regions. Clearly this is
> work in progress but wanted to share what I have. PDF is the working
Thanks for sharing this. What mechanisms secure the data (streams?)
in transit between nodes? This isn't clear for me.
On Mon, Mar 21, 2011 at 10:01 AM, Milind Parikh wrote:
> Here's the document on Cassandra (0.7.4) across EC2 regions. Clearly this is
> work in progress but wanted to share
Recent discussion on the dev list
http://www.mail-archive.com/dev@cassandra.apache.org/msg01832.html
Aaron
On 19 Mar 2011, at 06:46, A J wrote:
> Just to add, all the telnet (port 7000) and cassandra-cli (port 9160)
> connections are done using the public DNS (that goes like
> ec2-.compute.
Just to add, all the telnet (port 7000) and cassandra-cli (port 9160)
connections are done using the public DNS (that goes like
ec2-.compute.amazonaws.com)
On Fri, Mar 18, 2011 at 1:37 PM, A J wrote:
> I am able to telnet from one region to another on 7000 port without
> issues. (I get the ex
I am able to telnet from one region to another on 7000 port without
issues. (I get the expected Connected to .Escape character is
'^]'.)
Also I am able to execute cassandra client on 9160 port from one
region to another without issues (this is when I run cassandra
separately on each region wit
have you confirmed connectivity through the different security groups
and that you're not being blocked between region:port < -- > region:
port ?
On Fri, Mar 18, 2011 at 6:20 PM, A J wrote:
> Thats exactly what I am doing.
>
> I was able to do the first two scenarios without any issues (i.e. 2
>
>From the us-west instance, are you able to connect to the us-east instance
using telnet on port 7000 and 9160?
If not, then you need to open those ports for communication (via your
Security Group)
Dave Viner
On Fri, Mar 18, 2011 at 10:20 AM, A J wrote:
> Thats exactly what I am doing.
>
> I w
Thats exactly what I am doing.
I was able to do the first two scenarios without any issues (i.e. 2
nodes in same availability zone. Followed by an additional node in a
different zone but same region)
I am stuck at the third scenario of separate regions.
(I did read the "Cassandra nodes on EC2 in
Hi AJ,
I'd suggest getting to a multi-region cluster step-by-step. First, get 2
nodes running in the same availability zone. Make sure that works properly.
Second, add a node in a separate availability zone, but in the same region.
Make sure that's working properly. Third, add a node that's i
Hello,
I am trying to setup a cassandra cluster across regions.
For testing I am keeping it simple and just having one node in US-EAST
(say ec2-1-2-3-4.compute-1.amazonaws.com) and one node in US-WEST (say
ec2-2-2-3-4.us-west-1.compute.amazonaws.com).
Using Cassandra 0.7.4
The one in east region
23 matches
Mail list logo
