[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-user
Subject:    Re: Cross DC replication failing
From:       Jeff Jirsa <jjirsa () gmail ! com>
Date:       2021-11-13 19:05:40
Message-ID: 9C40EB2E-D72C-4BB8-8AC6-ACA843A33C76 () gmail ! com
[Download RAW message or body]




> On Nov 13, 2021, at 10:25 AM, Inquistive allen <inquiallen@gmail.com> wrote:
> 
> 
> Hello team,
> Greetings.
> 
> Simple question
> 
> Using Cassandra 3.0.8
> Writing to DC-A using local_quorum
> Reading the same data from a DC-B using local quorum.
> 
> It succeeds for a table and fails for other.
> Data written is not replicated immediately even after a long time.
> However if read is performed using a quorum we fetch data.
> 
> I do understand what is happening
> 
> Any idea
> 1. How to track how many messages are yet to be replicated

Potentially pending hints but not really



> 2. Any way to understand why they are not getting replicated across DC

Logs and tracing

> 3. I know I can force a sync by repair but this cross DC replication is expected to \
> be automatic. Am I correct?


Yes
This is probably some form of bug or configuration error. 3.0.8 is quite old and has \
a lot of known bugs, I'd start by upgrading to newest 3.0 or 3.11 or 4.0


[prev in list] [next in list] [prev in thread] [next in thread]