You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Andrei Yu (Jira)" <ji...@apache.org> on 2021/11/19 15:39:00 UTC

[jira] [Comment Edited] (KAFKA-13406) Cooperative sticky assignor got stuck due to assignment validation failed

    [ https://issues.apache.org/jira/browse/KAFKA-13406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17446540#comment-17446540 ] 

Andrei Yu edited comment on KAFKA-13406 at 11/19/21, 3:38 PM:
--------------------------------------------------------------

[~showuon] Seems the issue is fixed. Thank you for backporting it to 2.8 as well (y)


was (Author: andy_dufresne):
[~showuon]seems the issue is fixed. Thank you for backporting it to 2.8 as well (y)

> Cooperative sticky assignor got stuck due to assignment validation failed
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-13406
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13406
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 3.0.0
>            Reporter: Luke Chen
>            Assignee: Luke Chen
>            Priority: Major
>             Fix For: 3.1.0, 3.0.1, 2.8.2
>
>
> We'll do validateCooperativeAssignment for cooperative assignor, where we validate if there are previously owned partitions directly transfer to other consumers without "revoke" step. However, the "ownedPartition" in subscription might contain out-of-dated data, which might cause the validation always failure.
> We should consider the short-term fix it by disabling validateCooperationAssignment for built-in cooperativeStickyAssignor because we've already consider the generation in the assignor, and discard the old generation ownedPartition if any.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)