Re: Node replacement failed in 2.2

Paulo, the tokens field for 2401:db00:2130:4091:face:0:13:0 shows "TOKENS: not present", on all live nodes. It means tokens are missing, right? What would cause this? Thanks. Dikang. On Fri, Nov 18, 2016 at 11:15 AM, Paulo Motta wrote: > What does nodetool gossipinfo

Re: Node replacement failed in 2.2

What does nodetool gossipinfo shows for endpoint /2401:db00:2130:4091:face:0:13:0 ? Does it contain the TOKENS attribute? If it's missing, is it only missing on this node or other nodes as well? 2016-11-18 17:02 GMT-02:00 Dikang Gu : > Hi, I encountered couple times that I

Node replacement failed in 2.2

Hi, I encountered couple times that I could not replace a down node due to error: 2016-11-17_19:33:58.70075 Exception (java.lang.RuntimeException) encountered during startup: Could not find tokens for /2401:db00:2130:4091:face:0:13:0 to replace 2016-11-17_19:33:58.70489 ERROR 19:33:58 [main]:

what operations don't update materialized views?

Hi, Are there any operations that skip updating the materialized views?

Re: Re : Generic keystore when enabling SSL

On Thu, Nov 17, 2016 at 10:52 AM, sai krishnam raju potturi wrote: > I would suggest you create your own Certificate Authority, and create a > generic keystore and trustore. FWIW, that's what we (WMF) do: https://github.com/eevans/cassandra-ca-manager -- Eric Evans

Re: Is it a must to run Cassandra repair in scheduled time

This is an informative piece on (anti-entropy) repairs: https://cassandra-zone.com/understanding-repairs/ 2016-11-18 8:12 GMT-02:00 wxn...@zjqunshuo.com : > Thanks Ben for the response. It's very helpfull and it's really what I > want. > > > *From:* Ben Dalling

Re: Does recovery continue after truncating a table?

I investigated source code and logs of killed node. I guess that unexpected writes are executed when truncation is being executed. Some writes were executed after flush (the first flush) in truncation and these writes could be read. These writes were requested as MUTATION by another node for

Re: Is it a must to run Cassandra repair in scheduled time

Thanks Ben for the response. It's very helpfull and it's really what I want. From: Ben Dalling Date: 2016-11-18 18:07 To: user Subject: Re: Is it a must to run Cassandra repair in scheduled time Hi Simon, See http://www.datastax.com/dev/blog/repair-in-cassandra for a good explanation.

Re: Is it a must to run Cassandra repair in scheduled time

Hi Simon, See http://www.datastax.com/dev/blog/repair-in-cassandra for a good explanation. Basically repair is not a good word because it suggests it is fixing something that is broken. This is not the case. It ensures the consistency across your cluster. Not running repairs is a VERY BAD

Is it a must to run Cassandra repair in scheduled time

Hi All, I'm new to Cassandra and from the mail chain seemed repair is an important thing to do. To avoid trouble in putting Cassandra in production environment, I have some questions. 1. What exactly does Cassandra repair do? 2. I saw someone do repair in scheduled time, daily or weekly. Is it a