Re: Setting DC in different geographical location

Ashish, *> So, with this speed, is it possible in cassandra to perform asynchronous write in new DC(India)? * Nope, however your consistency level choice on writes is the main control for this. You write to the local DC with LOCAL_* consistency would make the acks on write to the remote DC not ne

Re: owns (effective)? Cassandra 4 b4

I'm facing the same issue. It's also reported by @aholmberg in: Incorrect output in "nodetool status -r" [image: image.png] On

Re: Use NetworkTopologyStrategy for single data center and add data centers later

Never, ever use SimpleStrategy in production - that's my golden rule. It's extremely limiting if you do and a pain to change your mind later. On Thu, 28 Jan 2021 at 02:00, Carl Mueller wrote: > Yes, perform that as soon as possible. > > When you add a new datacenter, keyspaces that are SimpleStr

Re: Cassandra on ZFS: disable compression?

I have done this several times i.e disabling compression at the table level. Never had any issues. On Wed, 27 Jan 2021 at 01:37, Elliott Sims wrote: > The main downside I see is that you're hitting a less-tested codepath. I > think very few installations have compression disabled today. > > On

Re: owns (effective)? Cassandra 4 b4

Ah, missed the keyspace name there. My bad :-) On Wed, Feb 10, 2021 at 4:13 PM Bowen Song wrote: > In your example, the nodetool output depends on whether the keyspace name > is present in the "nodetool status" command line parameters. "nodetool > status" command without a keyspace name may not

Re: owns (effective)? Cassandra 4 b4

In your example, the nodetool output depends on whether the keyspace name is present in the "nodetool status" command line parameters. "nodetool status" command without a keyspace name may not show the effective ownerships, but it should always show the effective ownership information when you

Re: owns (effective)? Cassandra 4 b4

I don't think it's related specifically to 4.0 I can see this issue on 3.11 and even on previous versions as well. It occurs when the replication factor is not similar on all keyspaces. For example, if you have a cluster with 2 DCs and one of the keyspaces has a RF of DC1: 3 whie other keyspaces ha

Re: owns (effective)? Cassandra 4 b4

This appears to be the same issue reported in CASSANDRA-16273 affecting 4.0 and is currently open/unresolved. Cheers! >

Re: Increased read latency with Cassandra >= 3.11.7

Hi Nico, On Mon, Sep 14, 2020 at 03:51PM +0200, Nicolai Lune Vest wrote: > after upgrading my Cassandra nodes from version 3.11.6 to either > 3.11.7 or 3.11.8 I experience a significant increase in read latency Any update here? Does version 3.11.10 provide any improvement? Thanks, Johannes ---