Well, I do have a confession to make. It is actually scyllaDB and the latest version. As it is (generally) Cassandra compatible I naturally assumed that these items were in both applications.
Marc From: Jeff Jirsa <jji...@gmail.com> Sent: Thursday, June 26, 2025 7:35 PM To: user@cassandra.apache.org Cc: user@cassandra.apache.org Subject: Re: Recycled-Commitlogs EXTERNAL What version of cassandra is this? Recycling segments was a thing from like 1.1 to 2.2 but really very different in modern versions (and cdc / point in time backup mirrors some of the concepts around hanging onto segments) Knowing the version would be super helpful though Is this … 1.2? 2.0? On Jun 26, 2025, at 1:22 AM, guo Maxwell <cclive1...@gmail.com<mailto:cclive1...@gmail.com>> wrote: I guess it comes from the archive of commitlogs ，just guess~~~ But I think we need the cassandra's version and commitlog's configuration in cassandra.yaml, and commitlog_archiving.properties to determine this. Marc Hoppins <marc.hopp...@eset.com<mailto:marc.hopp...@eset.com>> 于2025年6月26日周四 16:08写道： Hi, I am not a data person but a Linux admin. One of our nodes has thousands of -rw-r--r-- 1 root root 33554432 Jun 24 15:11 Recycled-CommitLog-2-67041997483.log hanging around. Eventually they fill the filesystem. I have searched around and can find no mention of these recycled commits. Can anyone explain what they are for? Can I purge these in some graceful fashion with a service restart, a simple deletion, or a complete drain/restart of the node? Thanks Marc
