I would like to propose the following solution to CASSANDRA-17047,
CASSANDRA-18589, CASSANDRA-18591 etc. (the rationale and line of thought
included below) for pre-TCM Cassandra versions, and I'd love to hear your
feedback.
Definitions:
There are three states of knowledge of a node wrt to a
>
>
> With TCM a schema change bumps an epoch, this epoch is then serialized with
> every read command/partition update and the replica can check if it is
> behind
> or ahead of the coordinator. This allows the replica to either catch up
> with
> the coordinator before executing the read/write or
Hi, reply inline below
On Mon, Jun 26, 2023 at 06:39:09PM +0200, Jakub Zytka wrote:
> Hello,
>
> I want to discuss the possibilities of fixing CASSANDRA-18591 and
> CASSANDRA-18589 (~exceptions during reads), considering that TCM will
> become a reality soon.
> While both issues can be hit even
Hello,
I want to discuss the possibilities of fixing CASSANDRA-18591 and
CASSANDRA-18589 (~exceptions during reads), considering that TCM will
become a reality soon.
While both issues can be hit even on a single-node cluster, I think it's
important for the solution to be at least TCM-friendly and
