incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Michalski <mich...@opera.com>
Subject Re: Other nodes are seen down with rpc_address 0.0.0.0 in version 1.2.2
Date Fri, 01 Mar 2013 09:48:39 GMT
Yes, it's caused by bug described in CASSANDRA-5299. It's because 
PropertyFileSnitch is using RPC address to obtain DC name from 
cassandra-topology.properties file. As you use 0.0.0.0 for RPC and this 
IP cannot be found in this config file, C* crashes.

M.

W dniu 01.03.2013 10:43, Jean-Armel Luce pisze:
> Hi,
>
>
> I have upgraded to Cassandra 1.2.2.
> There are 16 nodes in my cluster in 2 datacenters (8 nodes in each
> datacenter).
> I am using NetworkTopologyStrategy.
>
> I have a problem when defining in my C* cluster the rpc_address: 0.0.0.0
> into cassandra.yaml to allow listening on all interface.
> (I didn't have this problem with version 1.2.0)
>
> In version 1.2.2,  when I execute nodetool status from one node, the other
> nodes are seen node.
>
>
> Datacenter: b1
> ==============
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address           Load       Tokens  Owns (effective)  Host
> ID                               Rack
> DN  10.234.72.135     ?          256     36.6%
> e2b2de81-47bd-4e99-baed-a70ef9cbbbbb  c01
> DN  10.234.72.134     ?          256     45.0%
> 54c3424d-a8aa-48d0-ad76-957fc4ddc50d  e01
> DN  10.234.72.141     ?          256     43.5%
> 64e14102-4400-4859-9b9f-4bf867a75187  e06
> DN  10.234.72.140     ?          256     35.4%
> 0b84a722-a51f-468e-a9fd-363f8915dd7e  e07
> DN  10.234.72.139     ?          256     34.0%
> 00fb36ee-d652-4b46-899a-d04262805fb9  e07
> DN  10.234.72.138     ?          256     36.3%
> 62378ac6-308b-4231-8bef-1abdf623444b  e03
> DN  10.234.72.137     ?          256     34.2%
> 859a7dff-b110-4e13-9a9e-c912e6f22f8f  e03
> DN  10.234.72.136     ?          256     34.8%
> 026a0b17-491c-4f1b-9e1b-813cfd87ce00  c01
> Datacenter: s1
> ==============
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address           Load       Tokens  Owns (effective)  Host
> ID                               Rack
> DN  10.98.255.139     ?          256     42.3%
> b5b8c733-261d-40e6-aa99-158ccb7a1b2a  g10
> DN  10.98.255.138     ?          256     37.3%
> 0d3ebd50-1e52-4d56-9fc0-956818877038  i02
> DN  10.98.255.137     ?          256     36.2%
> 70c91c40-dac6-4141-86a8-d5aa838d29c2  i02
> DN  10.98.255.136     ?          256     36.2%
> 5e890166-0581-4fe9-aada-bd9f95526f9e  a09
> UN  10.98.255.135     5.27 GB    256     35.3%
> e07e1f54-1ac4-460d-aee3-8ef8b0fa27d2  a09
> DN  10.98.255.134     ?          256     39.6%
> 8b1d5a28-fa66-45f5-baed-3e18d29dfbf2  h06
> DN  10.98.255.141     ?          256     37.7%
> f7f376c0-d1d4-4cf9-af8d-2dbe59d04753  h06
> DN  10.98.255.140     ?          256     35.3%
> ee74e11d-b74e-4004-a7e6-758e7de8981a  g10
>
> In the log file, I see this message in each node
>
> ERROR [WRITE-/10.234.72.134] 2013-03-01 10:33:02,571 CassandraDaemon.java
> (line 132) Exception in thread Thread[WRITE-/10.234.72.134,5,main]
> java.lang.RuntimeException: Unknown host /0.0.0.0 with no default configured
>          at
> org.apache.cassandra.locator.PropertyFileSnitch.getEndpointInfo(PropertyFileSnitch.java:90)
>          at
> org.apache.cassandra.locator.PropertyFileSnitch.getDatacenter(PropertyFileSnitch.java:113)
>          at
> org.apache.cassandra.locator.DynamicEndpointSnitch.getDatacenter(DynamicEndpointSnitch.java:127)
>          at
> org.apache.cassandra.net.OutboundTcpConnection.isLocalDC(OutboundTcpConnection.java:76)
>
> Is it the normal behavior ?
> Is it due to https://issues.apache.org/jira/browse/CASSANDRA-5299 ?
>
> Regards
> Jean Armel
>


Mime
View raw message