********* General Configuration **********
Controlled shutdown can fail for multiple reasons.
Controlled shutdown can fail for multiple reasons. This determines the number of retries when such failure happens
Before each retry, the system needs time to recover from the state that caused the previous failure (Controller fail over, replica lag etc).
Before each retry, the system needs time to recover from the state that caused the previous failure (Controller fail over, replica lag etc). This config determines the amount of time to wait before retrying.
********* Replication configuration **********
********* Log Configuration **********
The required acks before the commit can be accepted.
The required acks before the commit can be accepted. In general, the default (-1) should not be overridden.
********* Offset management configuration **********
Batch size for reading from the offsets segments when loading offsets into the cache.
Frequency at which to check for stale offsets.
Offsets older than this retention period will be discarded.
Compression codec for the offsets topic - compression may be used to achieve "atomic" commits.
The number of partitions for the offset commit topic (should not change after deployment).
The replication factor for the offset commit topic (set higher to ensure availability).
The offsets topic segment bytes should be kept relatively small in order to facilitate faster log compaction and cache loads
********* Socket Server Configuration **********
ZK host string
ZK host string
the max time that the client waits to establish a connection to zookeeper
the max time that the client waits to establish a connection to zookeeper
zookeeper session timeout
zookeeper session timeout
how far a ZK follower can be behind a ZK leader
how far a ZK follower can be behind a ZK leader
Configuration settings for the kafka server