[KAFKA-3968] fsync() is not called on parent directory when new FileMessageSet is flushed to disk

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.0.1, 0.10.0.0
• Fix Version/s: 3.0.0
• Component/s: log
• Labels: reliability
• Environment: Linux, ext4 filesystem
• Flags: Patch
• Assignee: Cong Ding
• Reporter: Andrey Neporada
• Created: 15/Jul/16 15:33
• Updated: 12/Oct/24 03:36
• Resolved: 03/Apr/21 00:35

Description

Kafka does not call fsync() on directory when new log segment is created and flushed to disk.

The problem is that following sequence of calls doesn't guarantee file durability:

fd = open("log", O_RDWR | O_CREATE); // suppose open creates "log"
write(fd);
fsync(fd);

If system crashes after fsync() but before parent directory have been flushed to disk, the log file can disappear.
This is true at least for ext4 on Linux.

Proposed solution is to flush directory when flush() is called for the first time.

Issue Links

• is duplicated by: KAFKA-4127 Possible data loss
• links to: GitHub Pull Request #1626
• links to: GitHub Pull Request #1626
• links to: GitHub Pull Request #10405
• links to: GitHub Pull Request #10680