Re: Issue replacing a dead node

2025-05-15 Thread Courtney
I checked all the logs and really couldn't find anything. I couldn't find any sort of errors in dmesg, system.log, debug.log, gc.log (maybe up the log level?), systemd journal...the logs are totally clean. It just stops gossiping all of a sudden at 22GB of data each time, then the old node retu

Re: Issue replacing a dead node

2025-05-15 Thread Bowen Song via user
The dead node being replaced went back to DN state indicating the new replacement node failed to join the cluster, usually because the streaming was interrupted (e.g. by network issues, or long STW GC pauses). I would start looking for red flags in the logs, including Cassandra's logs, GC logs,