[
https://issues.apache.org/jira/browse/KAFKA-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-18652.
-------------------------------------
Fix Version/s: 4.4.0
Resolution: Fixed
I removed "assignor name" for the list of configs we want to add, to resolve
this ticket.
Assignor name is somewhat orthogonal to the other config and should be tackled
independently.
> 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
> Assignee: Matthias J. Sax
> Priority: Major
> Labels: kip1071
> Fix For: 4.4.0
>
>
> Add the broker-side configurations to enable the high-availability assignor /
> warm-up tasks.
>
> h4. New properties
> ||Name||Type||Default||Doc||
> |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.|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
