suzhiking commented on code in PR #23803: URL: https://github.com/apache/kafka/pull/23803#discussion_r4605223398
########## docs/streams/developer-guide/streams-rebalance-protocol.md: ########## @@ -39,7 +39,7 @@ The following features are available in the current release: * **Core Streams Group Rebalance Protocol**: The `group.protocol=streams` configuration enables the dedicated streams rebalance protocol. This separates streams groups from consumer groups and provides a streams-specific group membership lifecycle and metadata management on the broker. -* **Sticky Task Assignor**: A basic task assignment strategy that minimizes task movement during rebalances is included. It is registered under the name `sticky` and is the default assignor. +* **Built-in Task Assignors**: Two task assignment strategies are included. The `sticky` assignor minimizes task movement during rebalances and is the default assignor. The `balanced` assignor spreads the tasks of each subtopology across processes and evens out the per-thread task load, at the price of moving more tasks when the group membership changes; it is the counterpart of the `HighAvailabilityTaskAssignor` of the classic protocol, without warmup tasks, which are not an assignor feature in the streams protocol, and without rack-aware placement, which neither built-in assignor implements yet. A group selects an assignor with the group configuration `streams.assignor.name`. * **Custom Task Assignors**: Brokers can be configured with custom task assignors via `group.streams.assignors`, which takes a list of built-in assignor names and fully qualified class names of custom `TaskAssignor` implementations. The first entry is the default assignor. An individual group selects one of the registered assignors by name with the group configuration `streams.assignor.name`; when unset, the group uses the first entry of `group.streams.assignors`. Custom implementations must be thread-safe, since a single instance is shared across all groups on a broker. Review Comment: Make sense -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
