[
https://issues.apache.org/jira/browse/KAFKA-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075022#comment-17075022
]
ASF GitHub Bot commented on KAFKA-6145:
---------------------------------------
ableegoldman commented on pull request #8425: KAFKA-6145: KIP-441 Move tasks
with caught-up destination clients right away
URL: https://github.com/apache/kafka/pull/8425
If a stateful task is intended to be moved to a client which is already
caught-up, we should not create a warmup task for it. Instead, just reassign
that task right away.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Warm up new KS instances before migrating tasks - potentially a two phase
> rebalance
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-6145
> URL: https://issues.apache.org/jira/browse/KAFKA-6145
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Reporter: Antony Stubbs
> Assignee: Sophie Blee-Goldman
> Priority: Major
> Labels: needs-kip
>
> Currently when expanding the KS cluster, the new node's partitions will be
> unavailable during the rebalance, which for large states can take a very long
> time, or for small state stores even more than a few ms can be a deal breaker
> for micro service use cases.
> One workaround would be two execute the rebalance in two phases:
> 1) start running state store building on the new node
> 2) once the state store is fully populated on the new node, only then
> rebalance the tasks - there will still be a rebalance pause, but would be
> greatly reduced
> Relates to: KAFKA-6144 - Allow state stores to serve stale reads during
> rebalance
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
