?????? ?????? ?????? t olerate how many nodes down in the cluster

Thanks all for your thorough explanation. -- -- ??: "Anuj Wadehra";; : 2017??7??28??(??) 0:49 ??: "User cassandra.apache.org"; "Peng Xiao"<2535...@qq.com>; : Re:

Re: Stress test

The user and password should be in -mode section, for example: ./cassandra-stress user profile=table.yaml ops\(insert=1\) -mode native cql3 user=** password=** http://docs.datastax.com/en/cassandra/3.0/cassandra/tools/toolsCStress.html /Jay On 7/27/17 2:46 PM, Greg Lloyd wrote: > I am trying to

Re: nodetool repair failure

Michael, thanks for the input. I don't think I'm going to need to upgrade to 3.11 for the sake of getting nodetool repair working for me. Instead, I have another plausible explanation and solution for my particular situation. First, I should say that disk usage proved to be a red herring. There

Stress test

I am trying to use the cassandra stress tool with the user profile=table.yaml arguments specified and do authentication at the same time. If I use the user profile I get an error Invalid parameter user=* if I specify a user and password. Is it not possible to specify a yaml and use

Re: write time for nulls is not consistent

Thank you Jeff. Please share once, the Patch is available for us to apply. > On Jul 27, 2017, at 2:12 PM, Jeff Jirsa wrote: > > > > On 2017-07-20 08:46 (-0700), "Jeff Jirsa" wrote: >> >> >> On 2017-07-20 08:17 (-0700), Nitan Kainth

Re: write time for nulls is not consistent

On 2017-07-20 08:46 (-0700), "Jeff Jirsa" wrote: > > > On 2017-07-20 08:17 (-0700), Nitan Kainth wrote: > > Jeff, > > > > It is really strange, look at below log, I inserted your data and then few > > additional; finally, the issue is reproduced: >

Error Exception in Repair Thread

Hello Cassandra Experts! I have seen the following errors in the system log when a scheduled nodetool repair operation runs on the cluster. Cassandra Version 3.0.10. Any thoughts or suggestions are welcome! ERROR [Repair#3794:3] 2017-07-27 17:47:22,000 CassandraDaemon.java:207 - Exception in

Re: Data Loss irreparabley so

We (The Last Pickle) maintain an open source tool to help manage repairs across your clusters called Reaper. It’s a lot easier to set up and manage than trying to manage it through cron. http://thelastpickle.com/reaper.html > On Jul 27, 2017, at 12:38 AM,

Re: nodetool repair failure

On 07/27/2017 12:10 PM, Mitch Gitman wrote: > I'm using Apache Cassandra 3.10. > this is a dev cluster I'm talking about. > Further insights welcome... Upgrade and see if one of the many fixes for 3.11.0 helped? https://github.com/apache/cassandra/blob/cassandra-3.11.0/CHANGES.txt#L1-L129 If

Re: nodetool repair failure

I want to add an extra data point to this thread having encountered much the same problem. I'm using Apache Cassandra 3.10. I attempted to run an incremental repair that was optimized to take advantage of some downtime where the cluster is not fielding traffic and only repair each node's primary

Re: 回复： 回复： tolerate how many nodes down in the cluster

Hi Peng,  Racks can be logical (as defined with RAC attribute in Cassandra configuration files) or physical (racks in server rooms).   In my view, for leveraging racks in your case, its important to understand the implication of following decisions: 1. Number of distinct logical RACs defined in

How to have nested collections in UDF/UDA

Hi , I have a tables as below: CREATE TABLE test.cs ( > pid bigint, > cid bigint, > stat_object text, > status int, > PRIMARY KEY (pid, cid) > ) WITH CLUSTERING ORDER BY (cid ASC) How can I have a function like below : CREATE or REPLACE FUNCTION test.countstatusobjs (state

Re: Uncaught exception on thread CounterMutationStage

Hi Jeff, thanks for the pointers! We upgraded to C* 3.11.0 now and the situation has improved a little bit, the node does not die completely any more, but the WriteTimeoutExceptions persists and still 'freeze' the node for a couple of minutes. > A single node with 20 cores and 256GB of RAM is

Re: Data Loss irreparabley so

In that vein, Cassandra support Auto compaction and incremental repair. Does this mean I have to set up cron jobs on each node to do a nodetool repair or is this taken care of by Cassandra anyways? How often should I run nodetool repair Greetings Daniel Jeff Jirsa schrieb am

unsubscribe

Thanks and regards, Subhankar - To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org

Re: 回复： 回复： tolerate how many nodes down in the cluster

Note that if you use more racks than RF you lose some of the operational benefit. e.g: you'll still only be able to take out one rack at a time (especially if using vnodes), despite the fact that you have more racks than RF. As Jeff said this may be desirable, but really it comes down to what your

Re: 回复： 回复： tolerate how many nodes down in the cluster

On 2017-07-26 19:38 (-0700), "Peng Xiao" <2535...@qq.com> wrote: > Kurt/All, > > > why the # of racks should be equal to RF? > > For example,we have 2 DCs each 6 machines with RF=3,each machine virtualized > to 8 vms , > can we set 6 racs with RF3? I mean one machine one RAC to avoid