Production Ready/Stable DataStax Java Driver

2016-05-08 Thread Anuj Wadehra
Hi, Which DataStax Java Driver release is most stable (production ready) for Cassandra 2.1? ThanksAnuj

Warning message even for batches targeting single partition

2016-05-08 Thread Bhuvan Rawal
Hi, I was testing unlogged batches of size 15 and encountered bunch of these messages which are filling up my disk: 2016-05-08 20:22:58,338 [WARNING] cassandra.protocol: Server warning: *Unlogged batch covering 1 partition detected* against tables [xyz.abc, xyz.123]. You should use a logged batch

Re: Production Ready/Stable DataStax Java Driver

2016-05-08 Thread Alex Popescu
Hi Anuj, All released versions of the DataStax Java driver are production ready: 1. they all go through the complete QA cycle 2. we merge all bug fixes and improvements upstream. Now, if you are asking which is currently the most deployed version, that's 2.1 (latest version 2.1.10.1 [1]). If yo

Re: Production Ready/Stable DataStax Java Driver

2016-05-08 Thread Anuj Wadehra
Thanks Alex !! We are starting to use CQL for the first time (using Thrift till now), so I think it makes sense to directly use Java driver 3.0.1 instead of 2.1.10. As 3.x driver supports all 1.2+ Cassandra versions, I would also like to better understand the motivation of having 2.1 releases si

Re: Production Ready/Stable DataStax Java Driver

2016-05-08 Thread Alex Popescu
On Sun, May 8, 2016 at 10:00 AM, Anuj Wadehra wrote: > As 3.x driver supports all 1.2+ Cassandra versions, I would also like to > better understand the motivation of having 2.1 releases simultaneously with > 3.x releases of Java driver. Hi Anuj, Both Apache Cassandra and the DataStax drivers a

Re: Warning message even for batches targeting single partition

2016-05-08 Thread Ben Slater
Hi Bhuvan, You’re correct that large unlogged batch on one partition isn’t an issue. The logging behaviour has been/is being changed - see this jira for a detailed discussion: https://issues.apache.org/jira/browse/CASSANDRA-10876 Cheers Ben On Mon, 9 May 2016 at 00:58 Bhuvan Rawal wrote: > H

RE: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot

2016-05-08 Thread Michael Fong
Hi, all, Haven't heard any responses so far, and this isue has troubled us for quite some time. Here is another update: We have noticed several times that The schema version may change after migration and reboot: Here is the scenario: 1. Two node cluster (1 & 2). 2. There are so

Nodetool Cleanup Problem

2016-05-08 Thread Jan Ali
Hi All, I use cassandra 3.4.When running 'nodetool cleanup' command , see this error? error: Expecting URI in variable: [cassandra.config]. Found[cassandra.yaml]. Please prefix the file with [file:///] for local files and [file:///] for remote files. If you are executing this from an external t

RE: Effectiveness of Scrub Operation vs SSTable previously marked in blacklist

2016-05-08 Thread Michael Fong
Hi, I have filed a jira ticket to keep tracked @ https://issues.apache.org/jira/browse/CASSANDRA-11624 Thanks! Sincerely, Michael Fong From: Marcus Eriksson [mailto:krum...@gmail.com] Sent: Wednesday, March 23, 2016 10:47 PM To: user@cassandra.apache.org Subject: Re: Effectiveness of Scrub O

Re: [C*3.0.3]lucene indexes not deleted and nodetool repair makes DC unavailable

2016-05-08 Thread Siddharth Verma
Hi Eduardo, Thanks for your help on stratio index problem As per your questions. 1. We ran nodetool repair on one box(no range repair), but due to it, entire DC was non responsive. It was up, but we were not able to connect. 2. RF is 3, and we have 2 DCs each with 3 nodes. 3. Consistency level