cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Jirsa <jji...@gmail.com>
Subject Re: Unexpected error while refreshing token map, keeping previous version (IllegalArgumentException: Multiple entries with same key ?
Date Thu, 20 Jun 2019 15:03:27 GMT
There’s a reasonable chance this is a bug in the Datastax driver - may want to start there
when debugging .

It’s also just a warn, and the two entries with the same token are the same endpoint which
doesn’t seem concerning to me, but I don’t know the Datastax driver that well

> On Jun 20, 2019, at 7:40 AM, Котельников Александр <a.kotelnikov@crpt.ru>
wrote:
> 
> It appears that no such warning is issued if I connected to Cassandra from a remote server,
not locally.
>  
> From: Котельников Александр <a.kotelnikov@crpt.ru>
> Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
> Date: Thursday, 20 June 2019 at 10:46
> To: "user@cassandra.apache.org" <user@cassandra.apache.org>
> Subject: Unexpected error while refreshing token map, keeping previous version (IllegalArgumentException:
Multiple entries with same key ?
>  
> Hey!
>  
> I’ve  just configured a test 3-node Cassandra cluster and run very trivial java test
against it.
>  
> I see the following warning from java-driver on each CqlSession initialization:
>  
> 13:54:13.913 [loader-admin-0] WARN  c.d.o.d.i.c.metadata.DefaultMetadata - [loader] Unexpected
error while refreshing token map, keeping previous version (IllegalArgumentException: Multiple
entries with same key: Murmur3Token(-1060405237057176857)=/127.0.0.1:9042 and Murmur3Token(-1060405237057176857)=/127.0.0.1:9042)
>  
> What does It mean? Why?
>  
> Cassandra 3.11.4, driver 4.0.1.
>  
> nodetool status
> Datacenter: datacenter1
> =======================
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address       Load       Tokens       Owns (effective)  Host ID                 
             Rack
> UN  10.73.66.36   419.36 MiB  256          100.0%            fafa2737-9024-437b-9a59-c1c037bce244
 rack1
> UN  10.73.66.100  336.47 MiB  256          100.0%            d5323ad0-f8cd-42d4-b34d-9afcd002ea47
 rack1
> UN  10.73.67.196  336.4 MiB  256          100.0%            74dffe0c-32a4-4071-8b36-5ada5afa4a7d
 rack1
>  
> The issue persists if I reset the cluster, just the token changes its value.
> Alexander

Mime
View raw message