Thanks for your help guys.
You were right, the problem actually came from a very heavy data treatment
that happens every 2 hours starting at midnight. The processing performance
was heavily affected causing one node to write hints because communication
with the other node was complicated.
Best
Hi,
On Mon, Jan 16, 2023 at 3:07 PM Loïc CHANEL via user <
user@cassandra.apache.org> wrote:
> So my question here is : am I missing a Cassandra internal process that is
> triggered on a daily basis at 0:00 and 2:00 ?
>
I bet, it's not a Cassandra issue. Have you any other metrics about your
My general advice for any time you see hints accumulating, consider that
smoke for the more pressing fire happening somewhere else. You correctly
identified the right path to consider, which is some sort of scheduled
activity. Cassandra doesn't have any scheduled internal jobs. Compactions
happen
Check if you see packet loss at this time
On Mon, Jan 16, 2023 at 4:08 PM Loïc CHANEL via user <
user@cassandra.apache.org> wrote:
> Hi team,
>
> I am currently running a 2-nodes Cassandra database. Although that's not
> the best setup, the cluster is doing pretty fine.
> Still, I noticed that
Hi team,
I am currently running a 2-nodes Cassandra database. Although that's not
the best setup, the cluster is doing pretty fine.
Still, I noticed that for (at least) 5 days now, one of my two nodes is
writing hints during the night, and then it recovers the data-sync with the
other node in the
