[
https://issues.apache.org/jira/browse/KAFKA-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041387#comment-17041387
]
ASF GitHub Bot commented on KAFKA-9481:
---------------------------------------
guozhangwang commented on pull request #8058: KAFKA-9481: Graceful handling
TaskMigrated and TaskCorrupted
URL: https://github.com/apache/kafka/pull/8058
----------------------------------------------------------------
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
> Improve TaskMigratedException handling on Stream thread
> -------------------------------------------------------
>
> Key: KAFKA-9481
> URL: https://issues.apache.org/jira/browse/KAFKA-9481
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Priority: Major
>
> Today we handle TaskMigratedException as one-task at a time, when 1) producer
> got fenced, 2) consumer got fenced, 3) adding records to closed tasks.
> When 1) and 2) happens, all tasks hosted by that thread should have migrated;
> and for 3) it only happens when we are closing a task but not clearing its
> corresponding record buffer.
> So a better exception handling is first better fixing 3) to also clear the
> record buffer when closing a task (clean or dirty), and then for 1/2) we can
> always treat it as all-tasks-are-migrated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
