Re: Upgrade from 2.1.11 to 3.0.5 leads to unstable nodes

Hi all, Just updated the ticket. It turned out it was libjemalloc segfaulting the JVM. Regardless of the Java version (tried to update but no improvement), new C* versions (maybe because they preload libjemalloc by default) seem to be affected. Cheers, Stefano On Thu, May 5, 2016 at 5:01 PM,

RE: SS Tables Files Streaming

Does repair really send SS Table files as is ? Wouldn’t data for tokens be distributed across SS Tables ? From: Jeff Jirsa [mailto:jeff.ji...@crowdstrike.com] Sent: Friday, May 6, 2016 2:12 PM To: user@cassandra.apache.org Subject: Re: SS Tables Files Streaming Also probably sstableloader /

Read Latency: How is it computed?

This should be straight forward, but I would like to have a confirmation from the experts. I have the following 2 tables, CREATE TABLE event (   event_id uuid,   ... 38 attributes ...   PRIMARY KEY (event_id) ) CREATE TABLE event_index (   index_key text,   time_token timeuuid,   event_id

Re: SS Tables Files Streaming

Also probably sstableloader / bulk loading interface (I don’t think any of these necessarily stream “as-is”, but that’s a different conversation I suspect) From: Jonathan Haddad Reply-To: "user@cassandra.apache.org" Date: Friday, May 6, 2016 at 1:52 PM To: "user@cassandra.apache.org"

Re: SS Tables Files Streaming

Repairs, bootstamp, decommission. On Fri, May 6, 2016 at 1:16 PM Anubhav Kale wrote: > Hello, > > > > In what scenarios can SS Table files on disk from Node 1 go to Node 2 as > is ? I’m aware this happens in *nodetool rebuild* and I am assuming this > does *not*

SS Tables Files Streaming

Hello, In what scenarios can SS Table files on disk from Node 1 go to Node 2 as is ? I'm aware this happens in nodetool rebuild and I am assuming this does not happen in repairs. Can someone confirm ? The reason I ask is I am working on a solution for backup / restore and I need to be sure

Re: tuning repairs and compaction options

> > Hi, we are running a 9 node cluster under load. The nodes are running in > EC2 on i2.2xlarge instances. Cassandra version is 2.2.4. One node was down > yesterday for more than 3 hours. So we manually started an incremental > repair this morning via nodetool (anti-entropy repair?) > > What we

enabling Solr on a DSE C* node

HI Folks; I am trying to have one of my DSE 4.7 C* nodes also function as a Solr node within the cluster. I have followed the docs in vain : https://docs.datastax.com/en/datastax_enterprise/4.0/datastax_enterprise/srch/srchInstall.html Any pointers would help. Thanks Jan

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

Hi, This is very interesting that there is a difference between vanilla Cassandra and DSC, I thought it was simply the same thing provided with a setup/package. -- Jacques-Henri Berthemet From: Eduardo Alonso [mailto:eduardoalo...@stratio.com] Sent: vendredi 6 mai 2016 07:36 To:

Re: LeveledCompaction sstable counts

On Fri, May 6, 2016 at 10:48 AM, Joseph Tech wrote: > Thanks, Eric. Just curious, at what point does the old sstables get deleted > from disk? When a table is compacted, any records with an expired TTL will not be written to the new table, (so in your case: Not less than 6

Re: Read data from specific node in cassandra

This still doesn’t guarantee the behavior you think it does. From: Siddharth Verma Reply-To: "user@cassandra.apache.org" Date: Friday, May 6, 2016 at 12:20 AM To: "user@cassandra.apache.org" Subject: Re: Read data from specific node in cassandra Hi, Whitelist worked perfectly. Thanks for

Re: Read data from specific node in cassandra

Please check if nodetool getendpoints be used, if you know the key (going by your problem description) On 6 May 2016 22:04, "Siddharth Verma" wrote: @Joseph, An incident we saw in production, and have a speculation as to how it might have occured. *A detailed

Re: Read data from specific node in cassandra

@Joseph, An incident we saw in production, and have a speculation as to how it might have occured. *A detailed description of use case* *Incident* We have a 2 DCs each with three nodes. And our keyspace has RF 3 per DC. read_repair_chance is 0.0 for all the tables. After a while(we run periodic

Re: Read data from specific node in cassandra

@Siddharth , is there any specific user case where this is required ; What if the mainHost goes down? On Fri, May 6, 2016 at 12:50 PM, Siddharth Verma < verma.siddha...@snapdeal.com> wrote: > Hi, > Whitelist worked perfectly. > Thanks for the help. > > In case, someone wants to use the same, the

SSTable count at 10K during repair (won't decrease)

- Cassandra 2.1.13  - SSDs - LeveledCompactionStrategy    - Range repair (not incremental) with Spotify's Reaper https://github.com/spotify/cassandra-reaper Problem : When we run a repair job sometimes the SSTable count goes to 10K on one of nodes (not always the same node). The Reaper is smart

Re: LeveledCompaction sstable counts

Thanks, Eric. Just curious, at what point does the old sstables get deleted from disk? On Fri, May 6, 2016 at 8:41 PM, Eric Evans wrote: > On Fri, May 6, 2016 at 8:15 AM, Joseph Tech wrote: > > Please let me know how to interpret the below

Re: LeveledCompaction sstable counts

On Fri, May 6, 2016 at 8:15 AM, Joseph Tech wrote: > Please let me know how to interpret the below output from cfstats, > especially the entry in bold. > > SSTable count: 947 > SSTables in each level: [1, 10, 104/100, 832, 0, 0, 0, 0, 0] This is showing you 9 levels, each

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

Hi Siddaharth: I have tested with apache cassandra 3.0.3 and cassandra-lucene-index-3.0.3.1 and works well but with dsc-cassandra-3.0.3 it does not delete the lucene files. Please, can you open an issue ? Refering to your second

LeveledCompaction sstable counts

Hi, Please let me know how to interpret the below output from cfstats, especially the entry in bold. SSTable count: 947 SSTables in each level: [1, 10, *104/100*, 832, 0, 0, 0, 0, 0] We are using C* 2.0.14.459 (DSE version 4.6.7). and the table has been created with :

on-disk size vs partition-size in cfhistograms

Hi, I am trying to get some baselines for capacity planning. The approach i took was to insert increasing number of rows into a replica of the table to sized, watch the size of the "data" directory (after doing nodetool flush and compact), and calculate the average size per row (total directory

Re: tuning repairs and compaction options

Hi Reik, You could always throttle your repair by running smaller chunks of the repair. See https://github.com/BrianGallew/cassandra_range_repair. Regarding the compaction, you can always change the compactionthroughput using `nodetool setcompactionthroughput`. Hope this helps, Jens On Fri,

tuning repairs and compaction options

Hi, we are running a 9 node cluster under load. The nodes are running in EC2 on i2.2xlarge instances. Cassandra version is 2.2.4. One node was down yesterday for more than 3 hours. So we manually started an incremental repair this morning via nodetool (anti-entropy repair?) What we can see is

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

Hi, I have 2 queries. We are using cassandra dsc 3.0.3 and stratio lucene indexes on tables. 1. when table is truncated, lucene index is not cleared for the same. we see that it still occupied space on disk. 2. when we run nodetool repair, all node are up (nodetool status) but we can't connect

Re: Read data from specific node in cassandra

Hi, Whitelist worked perfectly. Thanks for the help. In case, someone wants to use the same, the bellow code snippet might help them private final Cluster mainCluster; private final Session mainSession; . . . . . . . . . . . . . . . . . . . . . . String mainHost = "IP_of_machine"; . . . . . . .