[CASSANDRA-13962] should java.io.OutputStream.flush() be called on Commit log operations ?

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Component/s: Legacy/Local Write-Read Paths

Environment

cassandra 2.2.8

• Severity: Normal
• Assignee: Unassigned
• Reporter: Ilya Shipitsin
• Created: 18/Oct/17 09:25
• Updated: 16/Apr/19 09:29

Description

we run high loaded cassandra cluster on 2.2.8
when we reboot node, very often we observe broken commit log, like described here

https://stackoverflow.com/questions/33304367/cassandra-exiting-due-to-error-while-processing-commit-log-during-initializatio

I guess, that output is not flushed upon commit log write, I mean java.io.OutputStream.flush()

google also say, the same issue occur to sstables (they are written in more rare fashion, so we did not observe that practically)

any idea why output is not flushed ? is it done in purpose ?