[ 
https://issues.apache.org/jira/browse/KAFKA-13406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luke Chen updated KAFKA-13406:
------------------------------
    Description: 
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.

  was:
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 fix it by deserializing the subscription userData for 
generation info in validateCooperationAssignment.


> 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
>
> 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.3.4#803005)

Reply via email to