Re: Data repairing on one node questionably affects data on others

. Saludos Jean Carlo "The best way to predict the future is to invent it" Alan Kay On Tue, Apr 26, 2016 at 12:06 AM, ssiv...@gmail.com <mailto:ssiv...@gmail.com> <ssiv...@gmail.com <mailto:ssiv...@gmail.com>> wrote: Hi All, I have cluster of 7 nodes complet

Data repairing on one node questionably affects data on others

Hi All, I have cluster of 7 nodes completely balanced (each node owns ~500GB of data). And I have one keyspace and one table and three replicas. Than, I just failed one node's disk, replace it with a new one and started repairing. During that process I noticed that additional two nodes have

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

Note, that DataStax Enterprise still uses C* v2.1.. On 03/15/2016 08:25 PM, Kathiresan S wrote: Thank you all ! Thanks, Kathir On Tue, Mar 15, 2016 at 5:50 AM, ssiv...@gmail.com <mailto:ssiv...@gmail.com> <ssiv...@gmail.com <mailto:ssiv...@gmail.com>> wrote:

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

I think that it's not ready, since it has critical bugs. See emails about C* memory leaks On 03/15/2016 01:15 AM, Robert Coli wrote: On Mon, Mar 14, 2016 at 12:40 PM, Kathiresan S > wrote: We are planning for

Re: C* memory leak during compaction

Duplicate the answer from Russell Hatch On 03/14/2016 07:32 PM, Russell Hatch wrote: Of course, no problem. On Sat, Mar 12, 2016 at 3:35 PM, ssiv...@gmail.com <mailto:ssiv...@gmail.com> <ssiv...@gmail.com <mailto:ssiv...@gmail.com>> wrote: Hi, Thank

Re: Cassandra 3.2.1: Memory leak?

Hi, I'll duplicate here my email with the same issue "/I have 7 nodes of C* v2.2.5 running on CentOS 7 and using jemalloc for dynamic storage allocation. Use only one keyspace and one table with Leveled compaction strategy. I've loaded ~500 GB of data into the cluster with replication factor

Re: Possible to adjust tokens on a vnode cluster?

Hello John! I'm just wonder how often one of your cluster nodes failed/crashed/go_down or meets disks crashing? Looking for some sort of probability of hardware failure.. Thank you. On 01/19/2016 09:21 PM, John Sumsion wrote: I have a 24 node cluster, with vnodes set to 256. 'nodetool

Re: Cassandra Java Driver

015 04:48 PM, DuyHai Doan wrote: Check protocol version when you create your Cluster object on the client side Le 30 déc. 2015 13:33, "ssiv...@gmail.com <mailto:ssiv...@gmail.com>" <ssiv...@gmail.com <mailto:ssiv...@gmail.com>> a écrit : I've j

Re: Cassandra Java Driver

I've just tried to use cassandra-driver-core-3.0.0_rc1 and cassandra-driver-core-3.0.0_beta1 with C* 2.2.4 (cassandra-all-2.2.4). And neither of them can connect to the local cluster. But cassandra-driver-core-2.1.9. Am I doing wrong? Happy New Year! On 12/28/2015 04:08 PM, Alexandre Dutra

Re: Cassandra Java Driver

I set it to ProtocolVersion.V4 (the highest). On 12/30/2015 04:48 PM, DuyHai Doan wrote: Check protocol version when you create your Cluster object on the client side Le 30 déc. 2015 13:33, "ssiv...@gmail.com <mailto:ssiv...@gmail.com>" <ssiv...@gmail.com <ma

Re: Cassandra Java Driver

Sorry, setting protocol version to V4 doesn't work for C* 3.1.1. I sure, for C* 2.2.4 it will work...Will check On 12/30/2015 04:48 PM, DuyHai Doan wrote: Check protocol version when you create your Cluster object on the client side Le 30 déc. 2015 13:33, "ssiv...@gmail.com <mai

Re: Cassandra Java Driver

No...It doesn't work for C* 2.2.4 too..( On 12/30/2015 04:48 PM, DuyHai Doan wrote: Check protocol version when you create your Cluster object on the client side Le 30 déc. 2015 13:33, "ssiv...@gmail.com <mailto:ssiv...@gmail.com>" <ssiv...@gmail.com <mailto:ssiv.

Re: SSTable structure

+1 On 03/30/2015 11:38 AM, Pierre wrote: Hi, Does anyone know if there is a more complete and up to date documentation about the sstable files structure (data, index, stats etc.) than this one : http://wiki.apache.org/cassandra/ArchitectureSSTable I'm looking for a full specification,

Commitlog activities

Hi! I have the following keyspaces cqlsh SELECT * FROM system.schema_keyspaces; keyspace_name | durable_writes | strategy_class | strategy_options

memtable_offheap_space_in_mb and memtable_cleanup_threshold

Hi everyone! I do write only workload (into one column family) and experiment with offheap-objects memtable space. I set parameters to:/ //memtable_offheap_space_in_mb = 51200 # 50Gb// //memtable_cleanup_threshold = 0.99/ and expect that flush will not be triggered until available /memtable

Re: Which hector version is suitable for cassandra 2.0.6 ?

Hello, DS JD On 03/27/2014 01:06 PM, DE VITO Dominique wrote: Hi, -Message d'origine- De : ssiv...@gmail.com [mailto:ssiv...@gmail.com] Envoyé : jeudi 27 mars 2014 10:41 À : user@cassandra.apache.org Objet : Re: Which hector version is suitable for cassandra 2.0.6 ? On 03/27/2014 12

Re: Which hector version is suitable for cassandra 2.0.6 ?

If you're using C* v2 I suggest you to switch to the latest DataStax JavaDriver which the only one who supports C* v2. Also you can use Astyanax in order to switch to its API but having something like DS JavaDriver under the hood. It may be interesting for you

Re: Which hector version is suitable for cassandra 2.0.6 ?

On 03/27/2014 12:23 PM, user 01 wrote: Btw both Hector Datastax java driver are maintained by Datastax, both for java, this speaks for itself ! I'm not sure about the first statement. What do you mean at the second part of the sentence? They are Java-based, but has different API (and I find

Re: unstable write performance

280 sec: 865658 operations; 2661.5 current ops/sec; [INSERT AverageLatency(us)=3640.16] 290 sec: 865658 operations; 0 current ops/sec; It also may indicate that C* trying to finished active tasks and your write requests have been in the queue all 10 sec. Try to monitor C* doing*$watch nodetool

Re: Why select count(*) from .. hangs ?

Hi, What is your hardware, C* version, data structure and typical data size ? On 03/25/2014 06:36 PM, shahab wrote: Hi, I am quite new to Cassandra and trying to evaluate its feasibility for our application. In our application, we need to insert roughly 30 sensor data every 30 seconds