No rpc_address found for Cassandra host

[Rajesh Sindhu]

Getting No rpc_address found for cassandra host while making connection using java driver .

->no rpc found for host A in host' peers system table (ControlConnection.java:350)

Also tried "Select * from system.peers table "using cqlsh .

for ex. :- we have three cassandra host A,B,C.

connect Using host A (no rpc found for host A in sytem.peers table,but B and C have rpc address)

connect Using host B (no rpc found for host B in sytem.peers table,but A and C have rpc address)

connect Using host C (no rpc found for host A in sytem.peers table,but A and B have rpc address)

Anyone else face the same problem ?

[Alex Popescu]

This makes me think you have rpc_address set to 0.0.0.0. Please update it for each node to point to the IP of the node (an IP that is visible from the client machine)

To unsubscribe from this group and stop receiving emails from it, send an email to java-driver-us...@lists.datastax.com.

--

:- a)

Alex Popescu

Sen. Product Manager @ DataStax

@al3xandru

[Rajesh Sindhu]

Hi Alex,

It has been updated already . What are all the other possible reasons of the same problem.  

Thanks

Rajesh Sindhu

Junior Software Engineer

Zscaler Inc.

[Alex Popescu]

On Thu, Sep 26, 2013 at 12:09 PM, Rajesh Sindhu <rsi...@zscaler.com> wrote:

Hi Alex,

It has been updated already . What are all the other possible reasons of the same problem.  

I don't know "all the other possible reasons", but the 2nd I can think of is that the rpc_address is an IP that is not actually visible

from the client machine (e.g. for an AWS node, rpc_address set to the private IP).

[Rajesh Sindhu]

Thanks Alex,

We have updated DSE cassandra version in the cluster.

Should we update Datastax java driver version as well accordingly ?

We might be getting this error due to compatibility issue ,thoughts ?

[Alex Popescu]

You should always try to use the latest version of the driver. I don't think there's a compatibility issue (what DSE version are you using, what driver version?), but more of a bug that might have been fixed in the driver already.

[Rajesh Sindhu]

Alex,

DSE version :3.1.1 (cassandra 1.2.6.1)

Datastax java driver version : 1.0.3-dse

[Alex Popescu]

Could you please go through these connection requirements checklist https://github.com/datastax/java-driver/wiki/Connection-requirements? If you still cannot get it to work we'll need more details about your setup: 

1. where is your cluster running?

2. do you have any firewall?

3. cassandra.yaml files

4. the nodetool ring output (run it against each node)

[Sylvain Lebresne]

I believe that's a DSE issue. Basically you shouldn't have a line for node A when you do "select * from system.peers table" on node A. If you do, it's "a bug" (of Cassandra/DSE). But I believe some versions of DSE were mistakenly adding lines there which triggers the error logging you see. If I'm not mistaken, this has been fixed in recent versions of DSE in the sense that it doesn't add the buggy lines anymore, but I'm not sure it removes said lines if they exist, so you might have to do it manually. In other words, if on node A the system.peers table has a line for node A (with mostly null columns in particular), you can delete manually that line (same for line B on node B, etc.. obviously). If the lines do reappear after that, please let me know, I'll check with the DSE team. 

I'll note that the driver logs an error because it detects something is wrong, but in theory that shouldn't affect the driver more than that.

--

Sylvain