Re: system.peers table was not updated

2014-09-03 Thread Tyler Hobbs
The system.* tables are not replicated, so they can (and will) have different contents on different nodes. On Wed, Sep 3, 2014 at 10:50 AM, Pavel Kogan wrote: > I tried cqlsh command on other nodes and you are right! I had no idea that > cqlsh results could be node dependent. > > Thanks, > Pa

Re: system.peers table was not updated

2014-09-03 Thread Pavel Kogan
I tried cqlsh command on other nodes and you are right! I had no idea that cqlsh results could be node dependent. Thanks, Pavel On Wed, Sep 3, 2014 at 10:54 AM, Tyler Hobbs wrote: > > On Wed, Sep 3, 2014 at 6:44 AM, Pavel Kogan > wrote: > >> Why peers table contains only 2 out of 3 nodes? >

Re: system.peers table was not updated

2014-09-03 Thread Tyler Hobbs
On Wed, Sep 3, 2014 at 6:44 AM, Pavel Kogan wrote: > Why peers table contains only 2 out of 3 nodes? system.local has information for the local node, system.peers has information for all other nodes. -- Tyler Hobbs DataStax

system.peers table was not updated

2014-09-03 Thread Pavel Kogan
We use Cassandra 2.0.8. Probably after decommissioning nodes long time ago, but I am not sure. We are not using this cluster intensively. According to Jira, this problem was fixed in 2.0.5 https://issues.apache.org/jira/browse/CASSANDRA-6053 Anyway, I truncated peers table and restarted one node