What commitlog settings are you using? Default is periodic with 10s sync. That leaves you a 10s window on hard poweroff/crash.
I would also expect cassandra to cleanup and start cleanly, which version are you running? On Mon, Jul 26, 2021 at 1:00 PM Leon Zaruvinsky <leonzaruvin...@gmail.com> wrote: > Hi Cassandra community, > > We (and others) regularly run into commit log corruptions that are caused > by Cassandra, or the underlying infrastructure, being hard restarted. I > suspect that this is because it happens in the middle of a commitlog file > write to disk. > > Could anyone point me at resources / code to understand why this is > happening? Shouldn't Cassandra not be acking writes until the commitlog is > safely written to disk? I would expect that on startup, Cassandra should > be able to clean up bad commitlog files and recover gracefully. > > I've seen various references online to this issue as something that will > be fixed in the future - so I'm curious if there is any movement or > thoughts there. > > Thanks a bunch, > Leon >
