You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lucas Brutschy (Jira)" <ji...@apache.org> on 2026/02/03 14:21:00 UTC
[jira] [Updated] (KAFKA-18652) Extended set of streams-specific broker configurations
[ https://issues.apache.org/jira/browse/KAFKA-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucas Brutschy updated KAFKA-18652:
-----------------------------------
Labels: kip1071 (was: )
> Extended set of streams-specific broker configurations
> ------------------------------------------------------
>
> Key: KAFKA-18652
> URL: https://issues.apache.org/jira/browse/KAFKA-18652
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Reporter: Lucas Brutschy
> Priority: Major
> Labels: kip1071
>
> Add the broker-side configurations to enable the high-availability assignor / warm-up tasks (for EA).
>
> h4. New properties
> ||Name||Type||Default||Doc||
> |group.streams.min.session.timeout.ms|int|45s|The minimum session timeout.|
> |group.streams.max.session.timeout.ms|int|60s|The maximum session timeout.|
> |group.streams.min.heartbeat.interval.ms|int|5s|The minimum heartbeat interval.|
> |group.streams.max.heartbeat.interval.ms|int|15s|The maximum heartbeat interval.|
> |group.streams.acceptable.recovery.lag|long|10’000|The maximum acceptable lag (number of offsets to catch up) for a client to be considered caught-up enough to receive an active task assignment.|
> |group.streams.num.warmup.replicas|int|2|The maximum number of warmup replicas.|
> |group.streams.max.warmup.replicas|int|20|Maximum for dynamic configurations of the warmup replica configuration|
> |group.streams.task.offset.interval.ms|int|60s|The interval in which the task changelog offsets on a client are updated on the broker. The offsets are sent with the next heartbeat after this time has passed.|
> |group.streams.min.task.offset.interval.ms|int|15s|Minimum for dynamic configurations of the task offset interval. Used to restrict users of the cluster from sending the task changelog offsets too often.|
> |group.streams.assignor.name|string|null|The name of the task assignor used for all streams groups. Can be {{sticky}} or {{highly_available}} in AK.|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)