You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lucas Brutschy (Jira)" <ji...@apache.org> on 2024/02/28 15:46:00 UTC
[jira] [Assigned] (KAFKA-16261) MembershipManagerImpl.updateSubscription fails if already empty subscription
[ https://issues.apache.org/jira/browse/KAFKA-16261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucas Brutschy reassigned KAFKA-16261:
--------------------------------------
Assignee: Lucas Brutschy (was: Lianet Magrans)
> MembershipManagerImpl.updateSubscription fails if already empty subscription
> ----------------------------------------------------------------------------
>
> Key: KAFKA-16261
> URL: https://issues.apache.org/jira/browse/KAFKA-16261
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Affects Versions: 3.7.0
> Reporter: Andrew Schofield
> Assignee: Lucas Brutschy
> Priority: Critical
> Labels: client-transitions-issues, consumer-threading-refactor, kip-848-client-support
> Fix For: 3.8.0
>
>
> The internal SubscriptionState object keeps track of whether the assignment is user-assigned, or auto-assigned. If there are no assigned partitions, the assignment resets to NONE. If you call SubscriptionState.assignFromSubscribed in this state it fails.
> The easiest thing is perhaps to check SubscriptionState.hasAutoAssignedPartitions() to make sure that assignFromSubscribed is going to be permitted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)