Ec2 snitch with network topology strategy
I was thinking of leveraging ec2 snitch. But my question is then how do I give replica placement options? Or can I give snitch as ec2snitch and write the nodes cassandra-topology.prop and in give locator strategy at time of creating keyspace as network topology strategy. But will it work? And those who are struggling to deploy cassandra with across ec2 regions. 1. approach is to use milind's patch, it works but has some limitation. https://issues.apache.org/jira/browse/CASSANDRA-2362 2. openvpn is a good option but neverthless is futile with encryption available in 0.8.0 cassandra 3. Vijay has come up with a patch and so far tested I have not seen any jerks. https://issues.apache.org/jira/browse/CASSANDRA-2452 - its marked to be there in 0.8.2 release. -pankaj -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Ec2-snitch-with-network-topology-strategy-tp6528188p6528188.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
Re: advice for EC2 deployment
No, the nodes in the separate DC's are able to discover each other. But across the Dc's its not happening. I have double checked the config parameters, both require in amazon settings and cassandra.yaml before posting query here. has anybody got there nodes talking to each other across regions by just using public-dns? I am also looking into open vpn and how to deploy it. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/advice-for-EC2-deployment-tp6294613p6508278.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
Re: Inter node communication over UDP
I am working on version 0.7.6 of cassandra. I have been looking into the code to identify communication between nodes. it seems to me that both inter-node and servernode-client communication happens using thrift protocol, is my understanding correct? and the gossiper communication takes place using tcp and message queue? -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Inter-node-communication-over-UDP-tp6358459p6384978.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
Inter node communication over UDP
we are deploying cassandra over a huge cluster size and we think that inter node communication can become overload on nodes as the protocol used is TCP. Similarly gossip was earlier using udp but has been changed to use Tcp. Is there added advantage for using tcp over udp in cassandra both in gossip and data storage(internal storage and retrival, etc)? And how much development time i should expect to code udp? -pankaj -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Inter-node-communication-over-UDP-tp6358459p6358459.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
Re: advice for EC2 deployment
I have been trying to deploy Cassandra cluster across regions and for that I posted this "IP address resolution in MultiDC setup". But when it is to get nodes talking to each other on different regions say, us-east and us-west over private IP's of EC2 nodes I am facing problems. I am assuming if Cassandra is built for multi-DC setup it should be easily deployed with node1's DC1's public IP listed as seed in all nodes in DC2 and to gain idea about network topology? I have hit a dud for deployment in such scenario. Or is it there any way possible to use Private IP's for such a scenario in EC2, as Public Ip are less secure and costly? -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/advice-for-EC2-deployment-tp6294613p6309154.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
Re: advice for EC2 deployment
I have been trying to deploy Cassandra cluster across regions and for that I posted this "IP address resolution in MultiDC setup". But when it is to get nodes talking to each other on different regions say, us-east and us-west over private IP's of EC2 nodes I am facing problems. I am assuming if Cassandra is built for multi-DC setup it should be easily deployed with node1's DC1's public IP listed as seed in all nodes in DC2 and to gain idea about network topology? I have hit a dud for deployment in such scenario. Or is it there any way possible to use Private IP's for such a scenario in EC2, as Public Ip are less secure and costly? -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/advice-for-EC2-deployment-tp6294613p6309153.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
