Re: Keyspace/CF creation Timeouts

1. Make sure all nodes are up and running while you are trying to create the Keyspaces and Column Family. 2. What is the write consistency level u r using? On 25 October 2016 at 13:18, Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Hello All, > > I have recently started noticing

Re: metrics not resetting after running proxyhistograms or cfhistograms

That behavior went away with 2.2. https://issues.apache.org/jira/browse/CASSANDRA-11752 adds decay to it to make it recent data which is much better then just reseting on reads. Chris On Tue, Oct 25, 2016 at 2:06 PM, Andrew Bialecki < andrew.biale...@klaviyo.com> wrote: > We're running 3.6.

Keyspace/CF creation Timeouts

Hello All, I have recently started noticing timeouts while creating KS/CF. this is happening with increase in no.of keyspaces. Does anyone have an idea what to look for? as I don't see any error or exception in the logs. or is there some kind of parameter change required? C* Version: 2.1.16

Re: Keyspace/CF creation Timeouts

As you have many keyspaces and column family to be created that might be the reason that within the stipulated time response is not coming back and u r seeing time out. Can you pls check write_request_timeout_in_ms also? On 25 October 2016 at 14:55, Edward Capriolo wrote:

Re: Keyspace/CF creation Timeouts

I do not believe the ConsistencyLevel matters for schema changes. In recent versions request_timeout_in_ms has been replaced by N variables which allow different timeout values for different types of operations. You seem to have both a lot of keyspaces and column families. It seems likely that

Hotspots / Load on Cassandra node

Hello, When I am issuing nodetool status, I see the load ( in GB) on one of the node is high compare to the other nodes in my ring. I do not see any issues with the Data Modeling, and it looks like the Partition sizes are almost evenly sized and distributed across the nodes.  Repairs are

Re: Keyspace/CF creation Timeouts

1. Yes, all nodes are up and running, 2. We are using the Local_QUORUM. On Tue, Oct 25, 2016 at 1:28 PM, Surbhi Gupta wrote: > 1. Make sure all nodes are up and running while you are trying to create > the Keyspaces and Column Family. > 2. What is the write consistency

Re: Keyspace/CF creation Timeouts

No, I am not trying to create many column families. I already have 500 CF in my cluster and now I am trying to create one KS and 3 CF. write_request_timeout_in_ms = 1 -> 10 seconds On Tue, Oct 25, 2016 at 3:00 PM, Surbhi Gupta wrote: > As you have many keyspaces

Re: Hotspots / Load on Cassandra node

How do you know you don't have a data modeling issue? On Tue, Oct 25, 2016 at 9:53 PM Harikrishnan A wrote: > Hello, > > When I am issuing nodetool status, I see the load ( in GB) on one of the > node is high compare to the other nodes in my ring. > > I do not see any issues

Re: Hotspots / Load on Cassandra node

There were recent bugs in 2.1/2.2 that caused the load reported by nodetool status to be artificially high – is the size on disk consistent with the value reported by ‘nodetool status’ ? From: Harikrishnan A Reply-To: "user@cassandra.apache.org"

Re: Hotspots / Load on Cassandra node

Hi, can you check the size of your data directories on that machine to verify in comparison to the others? Have a look for snapshot directories which could still be there from a former table or keyspace. Regards, Jan Am 26. Oktober 2016 06:53:03 MESZ, schrieb Harikrishnan A

Re: Keyspace/CF creation Timeouts

What is the error getting logged in system.log ? On 25 October 2016 at 15:31, Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > No, I am not trying to create many column families. > I already have 500 CF in my cluster and now I am trying to create one KS > and 3 CF. > >

Cassandra snapshot JMX commands

Hello Cassandra-users, I have a question about issuing snapshot using JMX commands. - Issuing snapshot on a single column family: Nodetool command: nodetool snapshot -cf -t ** The equivalent JMX command is: run -d org.apache.cassandra.db -b org.apache.cassandra.db:type=StorageService

Re: Anticompaction Question

Hi Anubhav, According to the Datastax documentation here , after the anti-compaction process splits the ranges to repaired and un-repaired SSTables, they are compacted in their own separate pools. Regards, Rajath

Anticompaction Question

Hello, If incremental repairs are enabled, there is logic in every compaction strategy to make sure not to mix repaired and unrepaired SS Tables. Does this mean if some SS Table files are repaired and some aren't and incremental repairs don't work reliably, the unrepaired tables will never get

Re: Thousands of SSTables generated in only one node

Hi Jan, Thanks for the response. My SSTables are < 3MB and I have 3500+ SSTables in the folder. When you say if they are small do you think my file sizes are small ? I ran the nodetool compact nothing happened, then I ran nodetool scrub it removed 500 SSTables then it stopped. Thanks for that

Re: Thousands of SSTables generated in only one node

Hi Lahiru, maybe your node was running out of memory before. I saw this behaviour if available heap is low forcing to flush out memtables to sstables quite often. If this is that what is hitting you, you should see that the sstables are really small. To cleanup, nodetool compact would do

Thousands of SSTables generated in only one node

Hi Users, I have a single server code deployed with multiple environments (staging, dev etc) but they all use a single Cassandra cluster but keyspaces are prefixed with the environment name, so each server has its own keyspace to store data. I am using Cassandra 2.1.0 and using it to store

Re: Thousands of SSTables generated in only one node

Hi Lahiru, 2.1.0 is also quite old (Sep 2014) - and just from my memory I remembered that there was an issue whe had with cold_reads_to_omit: http://grokbase.com/t/cassandra/user/1523sm4y0r/how-to-deal-with-too-many-sstables

Re: Thousands of SSTables generated in only one node

+1 definitely upgrade to 2.1.16. You shouldn't see any compatibility issues client side when upgrading from 2.1.0. If scrub removed 500 SSTables that's quite worrying. If the mass SSTables are causing issues you can disconnect the node from the cluster using: nodetool disablegossip && nodetool

Delete and insert rows in one batch

Dear all, In my project, because it's a legacy system, I have to run below CQL statements in one batch: BEGIN BATCH delete from "Volume" where key='urn:storageos:Volume: abf3614c-cd26-40b4-8543-e2d84e2fae70:vdc1' and column1='thinVolumePreAllocationSize' and column2='' and column3=''; insert

Re: Thousands of SSTables generated in only one node

what are your disk hardware specs ? On Tue, Oct 25, 2016 at 8:47 AM, Lahiru Gamathige wrote: > Hi Users, > > I have a single server code deployed with multiple environments (staging, > dev etc) but they all use a single Cassandra cluster but keyspaces are > prefixed with

Re: Doing an upsert into a collection?

You could do this with a map instead of a list. *CREATE TABLE movie (* * id text,* * name text,* * ratings map,* * PRIMARY KEY ( id )* *);* *UPDATE movie SET ratings['bob'] = 5 WHERE id = 'terminator 3';* -- Michael Mior michael.m...@gmail.com 2016-10-24 18:16 GMT-04:00 Ali Akhtar

RE: incremental repairs with -pr flag?

Thanks. Sean From: Alexander Dejanovski [a...@thelastpickle.com] Sent: Monday, October 24, 2016 10:39 AM To: user@cassandra.apache.org Subject: Re: incremental repairs with -pr flag? Hi Sean, In order to mitigate its impact, anticompaction is not fully executed

Re: Thousands of SSTables generated in only one node

I have not read the entire thread so sorry if this is already mentioned. You should review your logs, a potential problem could be a corrupted sstable. In a situation like this you will notice that the system is repeatedly trying to compact a given sstable. The compaction fails and based on the

Re: Thousands of SSTables generated in only one node

We have seen the issue while using LCS that there were around 100K stables got generated and compactions were not able to catch up and node became unresponsive. The reason for that was one of the stable got corrupted and compaction was kind of hanging on that sstable and further sstables were