log.flush.interval.ms — Kafka Broker Configuration
The maximum time in ms that a message in any topic is kept in memory before flushed to disk. If not set, the value in log.
Description
The maximum time in ms that a message in any topic is kept in memory before flushed to disk. If not set, the value in log.flush.scheduler.interval.ms is used
Default Values by Kafka Version
| Kafka Version | Default Value |
|---|---|
| 0.8.0 | 3000 |
| 0.8.1 | None |
| 0.8.2 | Long.MaxValue |
| 0.9.0 | null |
| 0.10.0 | null |
| 0.10.1 | null |
| 0.10.2 | null |
| 0.11.0 | null |
| 1.0 | null |
| 1.1 | null |
| 2.0 | null |
| 2.1 | null |
| 2.2 | null |
| 2.3 | null |
| 2.4 | null |
| 2.5 | null |
| 2.6 | null |
| 2.7 | null |
| 2.8 | null |
| 3.0 | null |
| 3.1 | null |
| 3.2 | null |
| 3.3 | null |
| 3.4 | null |
| 3.5 | null |
| 3.6 | null |
| 3.7 | null |
| 3.8 | null |
| 3.9 | null |
| 4.0 | null |
| 4.1 | null |
| 4.2 | null |
Tuning Recommendation
| Profile | Recommended | Why |
|---|---|---|
| broker / durability | 1000 | If per-message fsync is too expensive, a 1-second periodic flush limits the data loss window to at most 1 second of writes in an OS crash scenario. This is a reasonable middle ground between pure OS-managed flushing (loss window = minutes) and per-message fsync. |
Related Configs
log.flush.interval.messages · num.io.threads
Manage Kafka configs across all your clusters with Conduktor Console — view, compare, and update configurations in one place.