Re: CASSANDRA-8072

One suggestion I have, after recent experience setting up a cluster, is that Cassandra can provide better troubleshooting information to novice such as I. e.g. listen address for seed node (node whose public IP is the same as the address given in seeds) shouldn't be set to localhost. Thanks On T

Re: CASSANDRA-8072

Forgot to update this thread. Early afternoon I was able to get 5 node cluster up and running by following the guideline below. Thanks for the help. On Tue, Feb 9, 2016 at 5:09 PM, Stefania Alborghetti < stefania.alborghe...@datastax.com> wrote: > Can you make sure you changed the listen addres

Re: CASSANDRA-8072

Can you make sure you changed the listen address on both hosts, using their respective public IP address and that the seeds and cluster name are the same on both hosts. The seeds should contain the public IP of the seed node. Then verify you can telnet from one host to the other and vice-versa usi

Re: CASSANDRA-8072

On XX.YY : # service iptables status iptables: Firewall is not running. I put public IP address for listen address on a non-seed node. I still got: INFO 18:14:17 OutboundTcpConnection using coalescing strategy DISABLED ERROR 18:14:48 Exception encountered during startup java.lang.RuntimeExce

Re: CASSANDRA-8072

Have you checked that you can telnet from one node to the other using the same ip and the internode port? I would put the public IP addresses of the seeds in the seed list and set the listen address to the public IP address for each node. There was a similar discussion

Re: CASSANDRA-8072

Thanks for the help, Stefania. By using "127.0.0.1" , I was able to start Cassandra on that seed node (XX.YY). However, on other nodes, I pointed seed to XX.YY and observed the following ? What did I miss ? INFO [main] 2016-02-08 16:44:56,607 OutboundTcpConnection.java:97 - OutboundTcpConnectio

Re: CASSANDRA-8072

CASSANDRA-8072 is not going to help you because the code that fails (checkForEndpointCollision()) should not execute for seeds. I think the problem is that there are no seeds in cassandra.yaml: - seeds: "XX.YY" If listen_address is localhost then try: - seeds: "127.0.0.1" On Tue, Feb 9, 2016

Re: CASSANDRA-8072

If I apply the fix from CASSANDRA-8072 onto a 2.1.12 cluster, which files should I replace ? Thanks On Mon, Feb 8, 2016 at 1:07 PM, Bhuvan Rawal wrote: > Your config looks fine to me, i tried reproducing the scenario by setting > localhost in listen_address,rpc_address and seed list, and it wo

Re: CASSANDRA-8072

Your config looks fine to me, i tried reproducing the scenario by setting localhost in listen_address,rpc_address and seed list, and it worked fine, I had earlier the node local ip in the 3 fields and it was working fine. Looks like there is some other issue here. On Tue, Feb 9, 2016 at 12:49 AM

Re: CASSANDRA-8072

Here it is: http://pastebin.com/QEdjtAj6 XX.YY is localhost in this case. On Mon, Feb 8, 2016 at 11:03 AM, Bhuvan Rawal wrote: > could you paste your cassandra.yaml here, except for commented out lines? > > On Tue, Feb 9, 2016 at 12:30 AM, Ted Yu wrote: > >> The issue I described was observed

Re: CASSANDRA-8072

could you paste your cassandra.yaml here, except for commented out lines? On Tue, Feb 9, 2016 at 12:30 AM, Ted Yu wrote: > The issue I described was observed on the seed node. > > Both rpc_address and listen_address point to localhost. > > bq. What addresses are there in the seed list? > > The I

Re: CASSANDRA-8072

The issue I described was observed on the seed node. Both rpc_address and listen_address point to localhost. bq. What addresses are there in the seed list? The IP of the seed node. I haven't come to starting non-seed node(s) yet. Thanks for the quick response. On Mon, Feb 8, 2016 at 10:50 AM,

Re: CASSANDRA-8072

Hi Ted, Have you specified the listen_address and rpc_address? What addresses are there in the seed list? Have you started seed first and after waiting for 30 seconds started other nodes? On Tue, Feb 9, 2016 at 12:14 AM, Ted Yu wrote: > Hi, > I am trying to setup a cluster with DSE 4.8.4 > >