Upsource's cassandra's commit log filled up its drive causing a BSOD. After booting and clearing some space the service was unable to start correctly, we figured due to a corrupt commit log. I cleared out the commit log (recommended for a similar issue here: https://upsource-support.jetbrains.com/hc/en-us/community/posts/203461764-Upsource-wont-start-Cassandra-errors-) which meant the service now starts, but all our reviews are gone. Our project configurations are fine and new reviews are being created normally. Unfortunately, I didn't have the foresight to just move it to a different drive so I don't have a backup recent enough to contain currently active reviews.
This isn't a massive problem as historical data isn't used that much and the most relevant stuff is still relatively fresh in developers' minds, but it is inconvenient to say the least.
Is it normal that the data/cassandra/data/reviews-* directory (and most others) contains no files, just a couple of empty directories? There are reviews in the system.
Is there a way to clean up commit logs safely without losing data?
Windows Server 2012 R2