Hi,
I want to bring up some important changes to how addresses should be handled in
Cassandra after 7544. As of 7544 a Cassandra instance (sometimes referred to as
a node in the code) can't be identified by an InetAddress. It can't be
identified for the purposes of the internal storage communi
Are you referencing a specific book or section of docs? Can you link that here
so there’s context?
--
Jeff Jirsa
> On Feb 8, 2018, at 8:21 AM, Mahdi Manavi wrote:
>
> As in the "search in lost data" section , we should get tombstone from
> atleast one node. We should use the database strate
As in the "search in lost data" section , we should get tombstone from
atleast one node. We should use the database strategy which keeps the
deleted data in a table. And in the filtring proccess it should triger
bloom filter and search in the table and in the case that the search has
result report
There is an existing CoordinatorReadLatency table metric. I am looking to
add CoordinatorWriteLatency table metric - however, before I attempt a shot
at it, would like to know if anyone has context around why we currently do
not have such metric (while we have the read metric) - if someone has
alre
Michael,
it looks like the issue was related to an invalid keyspace. After I
dropped one keyspace (with an invalid datacenter name) and and altered
another one the warning is gone. But I can not reproduce it, even when
recreating the the previous keyspaces.
Oliver
2018-02-02 18:41 GMT+01:00 Mich