Client Read Latency is too high during repair

I'm using cassandra java driver to access a small cassandra cluster * The cluster have 3 nodes in DC1 and 3 nodes in DC2 * The keyspace is originally created in DC1 only with RF=2 * The client had good read latency about 40 ms of 99 percentile under 100 requests/sec (measured at the client side)

Support/Consulting companies

Howdy, I'm looking for a list of support or consulting companies that provide contracting services related to Cassandra. Is there a comprehensive list somewhere? Alternatively could you folks tell me who you use? Thanks in advance for any replies! Roxy

Re: large number of pending compactions, sstables steadily increasing

Hi Ezra, Are you making frequent changes to your rows (including TTL'ed values), or mostly inserting new ones? If you're only inserting new data, it's probable using size-tiered compaction would work better for you. If you are TTL'ing whole rows, consider date-tiered. If leveled compaction is

RE: Support/Consulting companies

http://thelastpickle.com/ From: Roxy Ubi [mailto:roxy...@gmail.com] Sent: Friday, August 19, 2016 2:02 PM To: user@cassandra.apache.org Subject: Support/Consulting companies Howdy, I'm looking for a list of support or consulting companies that provide contracting services related to Cassandra.

Re: A question to updatesstables

Hi, There are two ways to upgrade SSTables: - online (C* must be UP): nodetool upgradesstables - offline (when C* is stopped): using the tool called "sstableupgrade".    It's located in the bin directory of Cassandra so depending on how you installed Cassandra, it may be on the path.    See

RE: A question to updatesstables

yes, we use Cassandra 2.1.11 in our latest release. From: Romain Hardouin [mailto:romainh...@yahoo.fr] Sent: 2016年8月19日 17:36 To: user@cassandra.apache.org Subject: Re: A question to updatesstables ka is the 2.1 format... I don't understand. Did you install C* 2.1? Romain Le Vendredi 19 août

Re: nodetool repair with -pr and -dc

Hi Romain, Thank you for your answer, I will open a ticket soon. Best -- Jérôme Mainaud jer...@mainaud.com 2016-08-19 12:16 GMT+02:00 Romain Hardouin : > Hi Jérôme, > > The code in 2.2.6 allows -local and -pr: > https://github.com/apache/cassandra/blob/cassandra-2.2. >

full and incremental repair consistency

Hello, I have a 2.2.6 Cassandra cluster with two DC of 15 nodes each. A continuous incremental repair process deal with anti-entropy concern. Due to some untraced operation by someone, we choose to do a full repair on one DC with the command : nodetool repair --full -local -j 4 Daily

Re: full and incremental repair consistency

Running repair with -local flag does not mark sstables as repaired, since you can't guarantee data in other DCs are repaired. In order to support incremental repair, you need to run a full repair without the -local flag, and then in the next time you run repair, previously repaired sstables are

RE: A question to updatesstables

Here is the error message in our log file: java.lang.RuntimeException: Incompatible SSTable found. Current version ka is unable to read file: /data/db/1/data/StorageOS/RemoteDirectorGroup/StorageOS-RemoteDirectorGroup-ic-37. Please run upgradesstables. at

Re: nodetool repair with -pr and -dc

Hi Jérôme, The code in 2.2.6 allows -local and -pr:https://github.com/apache/cassandra/blob/cassandra-2.2.6/src/java/org/apache/cassandra/service/StorageService.java#L2899 But... the options validation introduced in CASSANDRA-6455 seems to break this

Re: A question to updatesstables

ka is the 2.1 format... I don't understand. Did you install C* 2.1? Romain Le Vendredi 19 août 2016 11h32, "Lu, Boying" a écrit : #yiv1355196952 #yiv1355196952 -- _filtered #yiv1355196952 {font-family:宋体;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv1355196952

Re: A question to updatesstables

The actual error message could be very useful to diagnose the reason. There are warnings about incompatible formats which are safe to ignore (usually in the cache) and I have one time seen an issue with commit log archiving preventing a startup during upgrade. Usually there is something else

Re: nodetool repair with -pr and -dc

Hello, I've got a repair command with both -pr and -local rejected on an 2.2.6 cluster. The exact command was : nodetool repair --full -par -pr -local -j 4 The message is “You need to run primary range repair on all nodes in the cluster”. Reading the code and previously cited CASSANDRA-7450,

Re: A question to updatesstables

Ok... you said 2.0.10 in the original post ;-)You can't upgrade from 1.2 to 2.1.2.0.7 is the minimum. So upgrade to 2.0.17 (the latest 2.0.X) first, see  https://github.com/apache/cassandra/blob/cassandra-2.1/NEWS.txt#L244 Best, Romain Le Vendredi 19 août 2016 11h41, "Lu, Boying"

Re: full and incremental repair consistency

It makes sense. When you say "you need to run a full repair without the -local flag", do you mean I have to set the -full flag ? Or do you mean that the next repair without arguments will be a full one because sstables or not flagged ? By the way, I suppose the repair flag don't break sstable

Re: full and incremental repair consistency

When you say "you need to run a full repair without the -local flag", do you mean I have to set the -full flag ? Or do you mean that the next repair without arguments will be a full one because sstables or not flagged ? - Either way, with or without the flag will actually be equivalent when none

Re: full and incremental repair consistency

> - Either way, with or without the flag will actually be equivalent when > none of the sstables are marked as repaired (this will change after the > first inc repair). > So, if I well understand, the repair -full -local command resets the flag of sstables previously repaired. So even if I had

Re: Support/Consulting companies

Instaclustr ( Instaclustr.com ) also offers Cassandra consulting On Friday, August 19, 2016, wrote: > Yes, TLP is the place to go! > > Joe > > Sent from my iPhone > > On Aug 19, 2016, at 12:03 PM, Huang, Roger

Re: Client Read Latency is too high during repair

Never mind. I found the root cause. This has nothing to do with Cassandra and repair. Some web services called by the client caused the problem. On Fri, Aug 19, 2016 at 11:53 AM, Benyi Wang wrote: > I'm using cassandra java driver to access a small cassandra cluster > > *

Re: Support/Consulting companies

Yes, TLP is the place to go! Joe Sent from my iPhone > On Aug 19, 2016, at 12:03 PM, Huang, Roger wrote: > > http://thelastpickle.com/ > > > From: Roxy Ubi [mailto:roxy...@gmail.com] > Sent: Friday, August 19, 2016 2:02 PM > To: user@cassandra.apache.org > Subject:

Re: How to create a TupleType/TupleValue in a UDF

On Thu, Aug 18, 2016 at 12:57 PM, Drew Kutcharian wrote: > I’m running 3.0.8, so it probably wasn’t fixed? ;) > Hmm, would you mind opening a new JIRA ticket about that and linking it to CASSANDRA-11033? > > The CodecNotFoundException is very random, when I get it, if I

opscenter cluster metric API call - 400 error

Hi, I have upgraded my cluster to DSE 5.0.1 and Opscenter 6.0.1. I am testing Opscenter APIs to retrieve node/cluster metrics but I get 400 errors when I throw queries as like below. curl -vvv -H 'opscenter-session: xx' -G 'http:metrics//data-load' > GET /IDC/metrics//data-load HTTP/1.1

Re: Support/Consulting companies

There's also a list of companies that provide Cassandra-related services on the wiki: https://wiki.apache.org/cassandra/ThirdPartySupport Jim On Fri, Aug 19, 2016 at 3:37 PM, Chris Tozer wrote: > Instaclustr ( Instaclustr.com ) also offers Cassandra consulting > >