gossip down failure detected

Hi, We are experiencing the following issue,the rt will fly to 15s sometime.and after adjusting the batch size, it looks better,but still have the following issue.Could any one advise? INFO [GossipTasks:1] 2017-07-07 08:56:33,410 Gossiper.java:1009 - InetAddress /172.16.xx.39 is now DOWN on

Re: Repair on system_auth

You can also stop repair using JMX without restarting. There are scripts to do that. Hannu > On 6 Jul 2017, at 23.24, ­Fay Hou [Storage Service] > wrote: > > There is a bug on repair system_auth keyspace. We just skip the repair on > system_auth. Yes. it is ok to kill

Re: Repair on system_auth

There is a bug on repair system_auth keyspace. We just skip the repair on system_auth. Yes. it is ok to kill the running repair job On Thu, Jul 6, 2017 at 1:14 PM, Subroto Barua wrote: > you can check the status via nodetool netstats > to kill the repair job,

Re: Repair on system_auth

you can check the status via nodetool netstatsto kill the repair job, restart the instance On Thursday, July 6, 2017, 1:09:42 PM PDT, Mark Furlong wrote: I have started a repair on my system_auth keyspace. The repair has started and the process shows as running with

Repair on system_auth

I have started a repair on my system_auth keyspace. The repair has started and the process shows as running with ps but am not seeing any CPU with top. I’m also note seeing any antientropy sessions building merkle trees in the log. Can I safely kill a repair and how? Mark Furlong Sr.

Re: need help tuning dropped mutation messages

c* version: 3.0.11 cross_node_timeout: truerange_request_timeout_in_ms: 1write_request_timeout_in_ms: 2000counter_write_request_timeout_in_ms: 5000cas_contention_timeout_in_ms: 1000 On Thursday, July 6, 2017, 11:43:44 AM PDT, Subroto Barua wrote: I am seeing

need help tuning dropped mutation messages

I am seeing these errors: MessagingService.java: 1013 -- MUTATION messages dropped in last 5000 ms: 0 for internal timeout and 4 for cross node timeout write consistency @ LOCAL_QUORUM is failing on a 3-node cluster and 18-node cluster..

Re: Simulating Read and WriteTimeouts programatically

On 2017-07-06 10:08 (-0700), "Charulata Sharma (charshar)" wrote: > An easier way to raise the ReadTimeOut and WriteTimeOutExceptions > programmatically and then test. However, I haven't had much success . > http://www.scassandra.org/ "Stubbed Cassandra is an open

Re: Guaranteed order for syncing Records

On 2017-07-05 23:14 (-0700), suraj pasuparthy wrote: > thanks Pranay, > But is the order maintained across tables? > As in the client in DC1 first writes record A in table A and then > immediately writes Record B in Table B, > So will the order be maintained, where

Re: Deflate compressor

On 2017-07-06 01:37 (-0700), Cogumelos Maravilha wrote: > Hi Jeff, > > Thanks for your reply. But I've already changed from LZ4 to Deflate to > get higher compression level. Can I in the Deflate compressor do the > same, set for a higher level of compression?

Re: Simulating Read and WriteTimeouts programatically

You can set timeout value in cqlshrc file. But you will have to overload the cluster to take these into effect. Sent from my iPhone > On Jul 6, 2017, at 10:08 AM, Charulata Sharma (charshar) > wrote: > > Hi All, > > Recently I learnt that in C* driver versions

Simulating Read and WriteTimeouts programatically

Hi All, Recently I learnt that in C* driver versions 3.1.x and up, there is a change in retry. If the query statement is not idempotent, there won't be any retry and by default the queries are considered to be non idempotent. Hence, even though Retry policy is mentioned while setting up the C*

Re: Cannot achieve consistency level LOCAL_ONE

Hi, I am facing similar issues with SYSTEM_AUTH keyspace and wanted to know the implication of disabling the "cassandra" superuser. Thanks, Charu From: "wxn...@zjqunshuo.com" > Date: Wednesday, June 14, 2017 at

Re: UDF for sorting

Hi Jeff: Do you mean something like this ? This is so basic(with no code change ) that i I have skipped the JIRA ticket creation Could you please review? Thank you Eduardo Alonso Vía de las dos Castillas, 33, Ática 4, 3ª Planta 28224 Pozuelo de

Re: Deflate compressor

Hi Jeff, Thanks for your reply. But I've already changed from LZ4 to Deflate to get higher compression level. Can I in the Deflate compressor do the same, set for a higher level of compression? Another question to the creator of the TimeWindowsCompactionStrategy: AND compaction = {'class':

Re: Guaranteed order for syncing Records

Cassandra uses the writetime to resolve the conflict. Highest time stamp wins. There's no guarantee on the order the mutations arrive in. On Thu, Jul 6, 2017 at 7:14 AM suraj pasuparthy wrote: > thanks Pranay, > But is the order maintained across tables? > As in the

Re: Guaranteed order for syncing Records

thanks Pranay, But is the order maintained across tables? As in the client in DC1 first writes record A in table A and then immediately writes Record B in Table B, So will the order be maintained, where in Table A gets synced first and then Table B? Thanks again -Suraj On Wed, Jul 5, 2017 at

Re: Guaranteed order for syncing Records

Hello suraj, Nope there will no out sync between same tables in different Datacenters, so Record A in Table A in Datacenter 1 will also be in Table A in Datacenter 2, just make sure there is no communication issues between Datacenters. Thanks Pranay. On Thu, Jul 6, 2017 at 2:01 AM, suraj

Guaranteed order for syncing Records

Hello Experts, I had a question We have a multi DC cluster for cassandra and wanted to confirm one behavior. Are the records order maintained while syncing to the backup datacenter? What i mean is, if say, Record A is written to a Table A and Record B is written to Table B on Datacenter 1, Does