How to get current value of commitlog_segment_size_in_mb?

Hi, In my project I need to read current value for "commitlog_segment_size_in_mb", I am looking for CQL query to do this. Any idea if this information gets stored in any of the Cassandra system table? Thanks, Jaydeep

Inconsistent results with Quorum at different times

Hi, We have three node (N1, N2, N3) cluster (RF=3) and data in SSTable as following: N1: SSTable: Partition key K1 is marked as tombstone at time T2 N2: SSTable: Partition key K1 is marked as tombstone at time T2 N3: SSTable: Partition key K1 is valid and has data D1 with lower time-stamp T1 (T

Lightweight tx is good enough to handle counter?

We have a following table: create table mytable { id int, count int static, rec_id int, primary key (id, rec_id) }; The count in the table represents how many records (rec_id clustering columns) exists. So when we add new a new record we do it following way: UNLOGGED BATCH insert into mytable

Re: Lightweight tx is good enough to handle counter?

Fri, Sep 23, 2016 at 8:10 PM, Jaydeep Chovatia < > chovatia.jayd...@gmail.com> wrote: > >> We have a following table: >> >> create table mytable { >> >> id int, >> count int static, >> rec_id int, >> primary key (id, rec_id) >> >

Re: Lightweight tx is good enough to handle counter?

Since SERIAL consistency is not supported for batch updates, I used QUORUM for the operation. On Fri, Sep 23, 2016 at 11:23 AM, DuyHai Doan wrote: > What is the consistency level used for the batch query ? > > > On Fri, Sep 23, 2016 at 8:19 PM, Jaydeep Chovatia < > chovatia

Re: Cassandra WriteTimeoutException

Are you using light weight transactions anywhere? On Wed, Jul 15, 2015 at 7:40 AM, Michael Shuler wrote: > On 07/15/2015 02:28 AM, Amlan Roy wrote: > >> Hi, >> >> I get the following error intermittently while writing to Cassandra. >> I am using version 2.1.7. Not sure how to fix the actual issu

High read latency

Hi, My application issues more read requests than write, I do see that under load cfstats for one of the table is quite high around 43ms Local read count: 114479357 Local read latency: 43.442 ms Local write count: 22288868 Local writ

Re: High read latency

Execution time of the GC > > > > 43ms for a read latency may be acceptable according to the number of > request per second. > > > > > > Eric > > > > *De :* Jaydeep Chovatia [mailto:chovatia.jayd...@gmail.com] > *Envoyé :* mardi 22 septembr

Re: High read latency

select * from test where a = ? and b = ? On Tue, Sep 22, 2015 at 10:27 AM, sai krishnam raju potturi < pskraj...@gmail.com> wrote: > thanks for the information. Posting the query too would be of help. > > On Tue, Sep 22, 2015 at 11:56 AM, Jaydeep Chovatia < > chovatia.jay

Re: High read latency

t;> thanks for the information. Posting the query too would be of help. >> >> On Tue, Sep 22, 2015 at 11:56 AM, Jaydeep Chovatia < >> chovatia.jayd...@gmail.com> wrote: >> >>> Please find required details here: >>> >>> - Number of r

Re: High read latency

neck was hit somewhere, or > the CPU got slammed with GC, or other processes running on the machine were > contending with Cassandra. > > > On Sep 25, 2015, at 12:45 PM, Jaydeep Chovatia > wrote: > > I understand that but everything is in RAM (my data dir is tmpfs) and my

Re: High read latency

t; >>> Anyway this is why I asked for the histograms, I wanted to get cell >>> count and partition size. I’ve seen otherwise very stout hardware get slow >>> on reads of large results because either a bottleneck was hit somewhere, or >>> the CPU got slammed

Re: Debugging write timeouts on Cassandra 2.2.5

Are you guys using light weight transactions in your write path? On Thu, Feb 11, 2016 at 12:36 AM, Fabrice Facorat wrote: > Are your commitlog and data on the same disk ? If yes, you should put > commitlogs on a separate disk which don't have a lot of IO. > > Others IO may have great impact impa

Re: High Bloom filter false ratio

How many partition keys exists for the table which shows this problem (or provide nodetool cfstats for that table)? On Thu, Feb 18, 2016 at 11:38 AM, daemeon reiydelle wrote: > The bloom filter buckets the values in a small number of buckets. I have > been surprised by how many cases I see with

Re: High Bloom filter false ratio

; > Latencies seem to have higher ratios, attached is the graph. > > > I am mostly trying to look at Bloom filters, because the way we do reads, > we read data with non existent partition keys and it seems to be taking > long to respond, like for 720 queries it takes 2 seconds, wit

Re: Regarding cassandra-stress results

ms On Mon, Mar 14, 2016 at 11:38 AM, Rajath Subramanyam wrote: > Hello Cassandra Community, > > When cassandra-stress tool dumps the output at the end of the benchmarking > run, what is the unit of latency statistics ? > > latency mean : 0.7 [READ:0.7, WRITE:0.7] > latency median

CQL performance inserting multiple cluster keys under same partition key

Hi, I have question on inserting multiple cluster keys under same partition key. Ex: CREATE TABLE Employee ( deptId int, empId int, name varchar, address varchar, salary int, PRIMARY KEY(deptId, empId) ); BEGIN *UNLOGGED *BATCH INSERT INTO Employee (deptId, empId, name, address,

Re: CQL performance inserting multiple cluster keys under same partition key

? On Tue, Aug 26, 2014 at 11:51 AM, Vivek Mishra wrote: > AFAIK, it is not. With CAS it should br > On 26/08/2014 10:21 pm, "Jaydeep Chovatia" > wrote: > >> Hi, >> >> I have question on inserting multiple cluster keys under same partition >> key.

Re: CQL performance inserting multiple cluster keys under same partition key

This clarifies my doubt. Thanks You Sylvain for your help. On Tue, Aug 26, 2014 at 11:59 PM, Sylvain Lebresne wrote: > On Tue, Aug 26, 2014 at 6:50 PM, Jaydeep Chovatia < > chovatia.jayd...@gmail.com> wrote: > >> Hi, >> >> I have question on inserting multiple

Re: Replacing a dead node by deleting it and auto_bootstrap'ing a new node (Cassandra 2.0)

as per my knowledge if you have externally NOT specified "-Dcassandra.replace_address=old_node_ipaddress" then new tokens (randomly) would get assigned to bootstrapping node instead of tokens of dead node. -jaydeep On Thu, Dec 4, 2014 at 6:50 AM, Omri Bahumi wrote: > Hi, > > I was wondering, ho

Re: Replacing a dead node by deleting it and auto_bootstrap'ing a new node (Cassandra 2.0)

0 PM, Omri Bahumi wrote: > I guess Cassandra is aware that it has some replicas not meeting the > replication factor. Wouldn't it be nice if a bootstrapping node would > get those? > Could make things much simpler in the Ops view. > > What do you think? > > On Fri, D

One node taking more resources than others in the ring

Hi, I have three node cluster with RF=1 (only one Datacenter) with following size: Datacenter: DC1 === Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- AddressLoad Tokens Owns Host ID Rack UN4.02 GB1 33.3%RAC1 UN4.05 GB1

Write timeout under load but Read is fine

Hi, In my test program when I increase load then I keep getting few "write timeout" from Cassandra say every 10~15 mins. My read:write ratio is 50:50. My reads are fine but only writes time out. Here is my Cassandra details: Version: 2.0.11 Ring of 3 nodes with RF=3 Node configuration: 24 core +

Re: Write timeout under load but Read is fine

gt;- check the time-outs if any on the client inserting the Writes >- check the Network for dropped/lost packets > > > hope this helps > Jan/ > > > > On Wednesday, March 4, 2015 12:26 PM, Jaydeep Chovatia < > chovatia.jayd...@gmail.com> wrote: > > &

Re: Write timeout under load but Read is fine

eliminate the client as the source of the error & also give you >> a replicable tool to base subsequent tests/ findings. >> >> Jan/ >> >> >> >> >> On Thursday, March 5, 2015 12:19 PM, Jaydeep Chovatia < >> chovatia.jayd...@gmail.com>

Re: nodetool repair -snapshot option?

Are you running full repair or on subset? If you are running full repair then try running on sub-set of ranges which means less data to worry during repair and that would help JAVA heap in general. You will have to do multiple iterations to complete entire range but at-least it will work. -jaydeep

Re: do all nodes actually send the data to the coordinator when doing a read?

Yes. Digest includes following: {name, value, timestamp, flags(deleted, expired, etc.)} On Fri, Jul 25, 2014 at 2:33 PM, DuyHai Doan wrote: > Thanks Mark for the very detailed explanation. > > However what's about timestamp checking ? You're saying that the > coordinator checks for the digest

Cassandra 0.7 C++ Thrift delete problem

Hi, I am facing some issues with delete operation in Cassandra-0.7.0 using C++ Thrift API. Please find details here: C++ Thrift Machine: Linux 64-bit 1. I am using remove thrift API to delete either column or column family. Problem in this is when I call remove then it hangs forever (never

Cassandra LongType data insertion problem

Hi, I have configured Cassandra Column Family (standard CF) of LongType. If I try to insert data (using batch_mutate) in this Column Family then it shows me following error: "A long is exactly 8 bytes". I have tried assigning column name of 8 bytes, 7 bytes, etc. but it shows same error. Pleas

Cassandra 3.0.14 transport completely blocked

Hi, I have been using Cassandra 3.0.14 in production for a long time. Recently I have found a bug in that, all of a sudden the transport thread-pool hangs. *Observation:* If I do *nodetool tpstats*, then it shows *"Native-Transport-Requests"* is blocking "Active" tasks. I stopped the complete tra

Re: Cassandra 3.0.14 transport completely blocked

several years ago, many critical bugs whose consequences include data loss > have been resolved. I'd strongly recommend upgrading to 3.0.26 - and > ideally to 4.0 after you've confirmed behavior is as expected on 3.0.26. > > – Scott > > On Mar 22, 2022, at 9:30 PM, Jaydee

Re: Cassandra 3.0.14 transport completely blocked

Please seriously consider upgrade your Cassandra cluster to the least > version. I can't tell which exact version fixed this bug, but we had > removed this from our servers many years ago after several rounds of > upgrades, and we have not had the NTR pool blocking issue coming back. &g

Re: Cassandra 3.0 upgrade

Thanks Jeff and Scott for valuable feedback! One more question, do we have to upgrade the dTest repo if we go to 3.0.27, or the one we have currently already working with 3.0.14 should continue to work fine? Jaydeep On Mon, Jun 13, 2022 at 10:25 PM C. Scott Andreas wrote: > Thank you for reachi

Re: Cassandra 3.0 upgrade

, you > probably don’t need to worry about the dtest repo. > > - Scott > > On Jun 13, 2022, at 10:36 PM, Jaydeep Chovatia > wrote: > >  > Thanks Jeff and Scott for valuable feedback! > One more question, do we have to upgrade the dTest repo if we go to > 3.0.27,

Re: Is cleanup is required if cluster topology changes

Isn't this considered a kind of *bug* in Cassandra because as we know *cleanup* is a lengthy and unreliable operation, so relying on the *cleanup* means higher chances of data resurrection? Do you think we should discard the unowned token-ranges as part of the regular compaction itself? What are th

Re: Is cleanup is required if cluster topology changes

; the ring is correct . > > > > On May 4, 2023, at 7:41 PM, Jaydeep Chovatia > wrote: > >  > Isn't this considered a kind of *bug* in Cassandra because as we know > *cleanup* is a lengthy and unreliable operation, so relying on the > *cleanup* means higher chance

Re: Is cleanup is required if cluster topology changes

ap. Stcs and twcs > are worse, but if you’re really scaling that often, I’d be considering lcs > and running cleanup just before or just after each scaling > > On May 4, 2023, at 9:25 PM, Jaydeep Chovatia > wrote: > >  > Thanks, Jeff! > But in our environment w

Re: Is cleanup is required if cluster topology changes

r@cassandra.apache.org> wrote: > >> Have you thought of using "-Dcassandra.replace_address_first_boot=..." >> (or "-Dcassandra.replace_address=..." if you are using an older version)? >> This will not result in a topology change, which means "nodetool cleanup"

Re: Is cleanup is required if cluster topology changes

ciate LCS anyway (faster reads, faster > data deletion than STCS). It's a lot of IO compared to STCS though. > > > > On Fri, May 5, 2023 at 9:02 AM Jaydeep Chovatia < > chovatia.jayd...@gmail.com> wrote: > >> Thanks all for your valuable inputs. We will try some of t

Re: Is cleanup is required if cluster topology changes

nvoke the code of *nodetool cleanup*? In other words, without CEP-21, why is *nodetool cleanup* a safer operation but doing the same in the regular compaction isn't? Jaydeep On Fri, May 5, 2023 at 11:58 AM Jaydeep Chovatia wrote: > Thanks, Jeff, for the detailed steps and summary. >

Re: Is cleanup is required if cluster topology changes

nsure the schema is consistent > across the cluster before running "nodetool cleanup". At the moment, it's > the operator's responsibility to ensure bad things don't happen. > On 09/05/2023 06:20, Jaydeep Chovatia wrote: > > One clarification question Jeff

Re: Replacing node without shutting down the old node

Hi Jeff, Do you think this is a good workaround to have in the Cassandra itself until we have CEP-21 available and cleanup as part of the compaction in the Cassandra itself? It can work as follows in C

Cassandra 4.0.6 token mismatch issue in production environment

Hi, I am using Cassandra 4.0.6 in production, and receiving the following error. This indicates that Cassandra nodes have mismatch in token-owership. Has anyone seen this issue before? Received a read request from /XX.XX.XXX.XXX:Y for a range that is not owned by the current replica Read(key

Re: Cassandra 4.0.6 token mismatch issue in production environment

nstead it’ll force it to read > from other replicas or time out) > > > > > > On Oct 20, 2023, at 10:57 PM, Jaydeep Chovatia > wrote: > >  > > Hi, > > I am using Cassandra 4.0.6 in production, and receiving the following error. > This indicates that

Re: Cassandra 4.0.6 token mismatch issue in production environment

want to drop the read log, >> which is the right solution so it doesn’t accidentally return a missing / >> empty result set as a valid query result, instead it’ll force it to read >> from other replicas or time out) >> >> >> >> >> >> On Oct 20,

Re: Cassandra 4.0.6 token mismatch issue in production environment

ssip / UP). A heap dump could have told us a bit more > conclusively, but it's hard to guess for now. > > > > On Mon, Oct 23, 2023 at 3:22 PM Jaydeep Chovatia < > chovatia.jayd...@gmail.com> wrote: > >> The issue was persisting on a few nodes despite no changes t

Race condition in QueryProcessor::prepare API

Hi, Today, in our production, we came across the following scenario: 1. We have 100 nodes of the Cassandra cluster on 4.0.6, and our client uses PreparedStatement, say, "*SELECT * FROM T1 WHERE PK=?*" 2. We applied a schema change to add a *regular* column, "*ALTER TABLE T1 ADD COLUMN

Re: Race condition in QueryProcessor::prepare API

/cassandra/cql3/QueryProcessor.java#L391> . Alex, could you please take a look at it? Jaydeep On Fri, Jan 19, 2024 at 7:17 PM Jaydeep Chovatia wrote: > Hi, > > Today, in our production, we came across the following scenario: > >1. We have 100 nodes of the Cassandra cluster o