check.crcs — Kafka Consumer Configuration
Automatically check the CRC32 of the records consumed. This ensures no on-the-wire or on-disk corruption to the messages occurred.
Description
Automatically check the CRC32 of the records consumed. This ensures no on-the-wire or on-disk corruption to the messages occurred. This check adds some overhead, so it may be disabled in cases seeking extreme performance.
Default Values by Kafka Version
| Kafka Version | Default Value |
|---|---|
| 0.9.0 | true |
| 0.10.0 | true |
| 0.10.1 | true |
| 0.10.2 | true |
| 0.11.0 | true |
| 1.0 | true |
| 1.1 | true |
| 2.0 | true |
| 2.1 | true |
| 2.2 | true |
| 2.3 | true |
| 2.4 | true |
| 2.5 | true |
| 2.6 | true |
| 2.7 | true |
| 2.8 | true |
| 3.0 | true |
| 3.1 | true |
| 3.2 | true |
| 3.3 | true |
| 3.4 | true |
| 3.5 | true |
| 3.6 | true |
| 3.7 | true |
| 3.8 | true |
| 3.9 | true |
| 4.0 | true |
| 4.1 | true |
| 4.2 | true |
Tuning Recommendation
| Profile | Recommended | Why |
|---|---|---|
| consumer / durability | true | CRC32 verification on every fetched record detects bit-level data corruption caused by disk errors, memory faults, or network corruption that slipped past TCP checksums. This is a critical integrity guard for durable pipelines where silent data corruption is worse than a detected error. |
Related Configs
fetch.max.bytes · max.poll.records
Manage Kafka configs across all your clusters with Conduktor Console — view, compare, and update configurations in one place.