Hello there, I’m running cassandra 3.11.0 and I have configured commitlog_archiving.properties to run a script. That script rsyncs the commit log files to a backup server. If the rsync is successful then the script exits with status 0 and the commit log file is deleted from the cassandra node. If the rsync is NOT successful then the script exits with status 1 and the commit log file is NOT deleted from the cassandra node.
Therefore when the backup server is down the commit log files start to pile up. Once the backup server is up again new commit log files will be synced to the backup server and deleted locally. The old commit log files (the ones that failed to sync earlier) do not get synced at all while cassandra is up. They will only get synced after the cassandra node is restarted. Is this what is expected? I would personally expect that all commit log syncs would resume at some point and the archiving status would return to normal. Many thanks Spyros --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
