Re: Cassandra Collections performance issue

Hello all, Recently we added one of the table fields from as Map in Cassandra 2.1.11. Currently we read every field from Map and overwrite map values. Map is of size 3. We saw that writes are 30-40% slower while reads are 70-80% slower. Please find below some metrics that can help.

Re: Cassandra Collections performance issue

ve a classic anti-pattern in play. ... Daemeon C.M. Reiydelle USA (+1) 415.501.0198 London (+44) (0) 20 8144 9872 On Mon, Feb 8, 2016 at 5:23 PM, Robert Coli <rc...@eventbrite.com<mailto:rc...@eventbrite.com>> wrote: On Mon, Feb 8, 2016 at 2:10 PM, Agrawal, Pratik <paagr...@

Cassandra unit tests broke after upgrading from Cassandra 2.0.9 to Cassandra 2.2.4

Hello all, In Cassandra 2.0.9 we used to unit test Cassandra Client side code by starting a local Cassandra server through code. We used to do the following: 1.) Initialize Yaml file by providing YAML file path: System.setProperty("cassandra.config", "file://" + TEMP_YAML_LOCATION); 2.)

FW: Cassandra unit tests broke after upgrading from Cassandra 2.0.9 to Cassandra 2.2.4

Hello all, In Cassandra 2.0.9 we used to unit test Cassandra Client side code by starting a local Cassandra server through code. We used to do the following: 1.) Initialize Yaml file by providing YAML file path: System.setProperty("cassandra.config", "file://" + TEMP_YAML_LOCATION); 2.)

Re: Re : Decommissioned nodes show as DOWN in Cassandra versions 2.1.12 - 2.1.16

We are seeing the same issue with Cassandra 2.0.8. The nodetool gossipinfo reports a node being down even after we decommission the node from the cluster. Thanks, Pratik From: kurt greaves > Reply-To:

Re: Hinted Handoff

Regards, Kyrill ________ From: Agrawal, Pratik Sent: Monday, August 6, 2018 8:22:27 PM To: user@cassandra.apache.org Subject: Hinted Handoff Hello all, We use Cassandra in non-conventional way, where our data is short termed (life cycle of about 20-30 minutes) where each record is updated ~5 tim

Re: Hinted Handoff

into other databases (like Redis, Aerospike). We have a write heavy use case and also need optimistic locking + columnar updates. Thanks, Pratik On 7 August 2018 at 07:20, Agrawal, Pratik mailto:paagr...@amazon.com.invalid>> wrote: Does Cassandra TTL out the hints after max_hint_windo

Hinted Handoff

Hello all, We use Cassandra in non-conventional way, where our data is short termed (life cycle of about 20-30 minutes) where each record is updated ~5 times and then deleted. We have GC grace of 15 minutes. We are seeing 2 problems 1.) A certain number of Cassandra nodes goes down and then

Re: Cassandra single unreachable node causing total cluster outage

from the cluster. 2. Is there a way to fail fast the NTR requests rather than being blocked on the NTR queue when the queue is full? Thanks, Pratik From: "Agrawal, Pratik" Date: Monday, December 3, 2018 at 11:55 PM To: "user@cassandra.apache.org" , Marc Selwan Cc: Jef

Re: Cassandra single unreachable node causing total cluster outage

e causing total cluster outage Ben's question is a good one - What are the exact symptoms you're experiencing? Is it latency spikes? Nodes flapping? That'll help us figure out where to look. When you removed the down node, which command did you use? Best, Marc On Sun, Dec 2, 2018 at 1:36 PM Agraw

Re: Cassandra single unreachable node causing total cluster outage

email and any attachments may contain confidential and legally privileged information. If you are not the intended recipient, do not copy or disclose its content, but please reply to this email immediately and highlight the error to the sender and then immediately delete the message. On Tue, 2

Cassandra single unreachable node causing total cluster outage

Hello all, Setup: 18 Cassandra node cluster. Cassandra version 2.2.8 Amazon C3.2x large machines. Replication factor of 3 (in 3 different AZs). Read and Write using Quorum. Use case: 1. Short lived data with heavy updates (I know we are abusing Cassandra here) with gc grace period of 15

Re: Cassandra single unreachable node causing total cluster outage

One other thing I forgot to add: native_transport_max_threads: 128 we have commented this setting out, should we bound this? I am planning to experiment with this setting to bound it. Thanks, Pratik From: "Agrawal, Pratik" Date: Sunday, December 2, 2018 at 4:33 PM