On Fri, May 22, 2020 at 9:51 PM Jeff Jirsa wrote:
> With those consistency levels it’s already possible you don’t see your
> writes, so you’re already probably seeing some of what would happen if you
> went to RF=5 like that - just less common
>
> If you did what you describe you’d have a 40% cha
In 2.2 and earlier, cql row deletes appear as range tombstones
All Range tombstones for a cql PARTITION get read into a list (I think it’s
literally RangeTombstoneList.java But I’m not at a computer to check ) at the
start of a read command and held in memory to reconcile the read
Because they
Hi Jeff
Could you elaborate on the statement that you made :
“CQL Row level tombstones don’t matter in cassandra 3+ - they’re just point
deletes after the storage engine rewrite.”
Are you saying that a row level delete is not like other tomestones ? if so how
are they different ?
I tried to googl
Hi all,
I have cassandra cluster (v3.11.6 with GossipingPropertyFileSnitch) with 2
datacenters named Zone1 and Zone2 each having 2 nodes. When all nodes are up
"nodetool status" shows correct cluster topology. When I bring down all nodes
except one, remaining node still shows correct topology.
