Thanks Scott. I will prioritize upgrading to 3.0.27 and will circle back if
this issue persists.
Jaydeep
On Tue, Sep 6, 2022 at 3:45 PM C. Scott Andreas
wrote:
> Hi Jaydeep,
>
> Thanks for reaching out and for bumping this thread.
>
> This is probably not the answer you’re after, but
Hi Jaydeep,Thanks for reaching out and for bumping this thread.This is probably not the answer you’re after, but mentioning as it may address the issue.C* 3.0.14 was released over five years ago, with many hundreds of important bug fixes landing since July 2017. These include fixes for issues that
If anyone has seen this issue and knows a fix, it would be a great help!
Thanks in advance.
Jaydeep
On Fri, Sep 2, 2022 at 1:56 PM Jaydeep Chovatia
wrote:
> Hi,
>
> We are running a production Cassandra version (3.0.14) with 256 tokens
> v-node configuration. Occasionally, we see that
Hi,
We are running a production Cassandra version (3.0.14) with 256 tokens
v-node configuration. Occasionally, we see that different nodes show
different ownership for the same key. Only a node restart corrects;
otherwise, it continues to behave in a split-brain.
Say, for example,
*NodeA*