[
https://issues.apache.org/jira/browse/KAFKA-13501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867956#comment-17867956
]
Colt McNealy commented on KAFKA-13501:
--------------------------------------
Matthias—the description makes sense, your comment is in line with what I
thought. I just saw the label `new-streams-runtime-should-fix` which was
related to the State Updater (it seemed _plausible_ that the State Updater
could have fixed this so I thought it wasn't in error).
On a separate note, how can I reproduce this error? Can I do it by forcing a
`RecordTooLargeException` or something like that? I'd like to verify this
behavior and potentially look into a fix; we haven't detected this yet in our
chaos tests but I would prefer that we catch it rather than our customers.
> Avoid state restore via rebalance if standbys are enabled
> ---------------------------------------------------------
>
> Key: KAFKA-13501
> URL: https://issues.apache.org/jira/browse/KAFKA-13501
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Priority: Major
> Labels: new-streams-runtime-should-fix
>
> There are certain scenario in which Kafka Streams wipes out local state and
> rebuilt it from scratch. This is a thread local cleanup, ie, no rebalance is
> triggered, and we end up with an offline task until state restoration
> finished.
> If standby tasks are enable, it might actually make sense to trigger a
> rebalance instead, to get the task re-assigned to the instance hosting the
> standby so get the task active again quickly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
