unsubscribe

2016-09-06 Thread dhanesh malviya
-- Regards, Dhanesh Malviya..

Re: Incremental repairs in 3.0

2016-09-06 Thread Bryan Cheng
HI Jean, This blog post is a pretty good resource: http://www.datastax.com/dev/blog/anticompaction-in-cassandra-2-1 I believe in 2.1.x you don't need to do the manual migration procedure, but if you run regular repairs and the data set under LCS is fairly large (what this means will probably depe

Isolation in case of Single Partition Writes and Batching with LWT

2016-09-06 Thread Bhuvan Rawal
Hi, We are working to solve on a multi threaded distributed design which in which a thread reads current state from Cassandra (Single partition ~ 20 Rows), does some computation and saves it back in. But it needs to be ensured that in between reading and writing by that thread any other thread sho

CASSANDRA-5376: CQL IN clause on last key not working when schema includes set,list or map

2016-09-06 Thread Samba
Hi, "CASSANDRA-5376: CQL IN clause on last key not working when schema includes set,list or map" is marked resolved in 1.2.4 but i still see the issue (not an Assertion Error, but an query validation message) was the issue resolved only to report proper error message or was it fixed to support r

Re: WriteTimeoutException with LOCAL_QUORUM

2016-09-06 Thread Romain Hardouin
1) Is it a typo or did you really make a giant leap from C* 1.x to 3.4 with all the C*2.0 and C*2.1 upgrades? (btw if I were you, I would use the last 3.0.X) 2) Regarding NTR all time blocked (e.g. 26070160 from the logs), have a look to the patch "max_queued_ntr_property.txt": https://issues.ap

Re: Incremental repairs in 3.0

2016-09-06 Thread Jean Carlo
Hi @Bryan When you said "sizable amount of data" you meant a huge amount of data right? Our big table is in LCS and if we use the migration process we will need to run a repair seq over this table for a long time. We are planning to go to repairs inc using the version 2.1.14 Saludos Jean Carlo

Re: How to start using incremental repairs?

2016-09-06 Thread Jean Carlo
Hi Paulo Can you clarify me please if what you said here 1. Migration procedure is no longer necessary after CASSANDRA-8004, and since you never ran repair before this would not make any difference anyway, so just run repair and by default (CASSANDRA-7250) this will already be incremental. appli

Re: Read timeouts on primary key queries

2016-09-06 Thread Romain Hardouin
There is nothing special in the two sstablemetadata outuputs but if the timeouts are due to a network split or overwhelmed node or something like that you won't see anything here. That said, if you have the keys which produced the timeouts then, yes, you can look for a regular pattern (i.e. alwa

Upgrade cassandra 2.1.14 to 3.0.7

2016-09-06 Thread Jean Carlo
Hello guys We are planing to upgrade cassandra soon to the version 3.0.7 from 2.1.14. Our concern is the repair, in 3.0.7 repairs inc are by default. Then it means that once we do the upgrade to 3.0.7 we must follow the migration process of repairs inc for all our data in order to mark the sstable