[jira] [Updated] (KAFKA-15592) Member does not need to always try to join a group when a groupId is configured
[ https://issues.apache.org/jira/browse/KAFKA-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15592: -- Fix Version/s: 3.7.0 > Member does not need to always try to join a group when a groupId is > configured > --- > > Key: KAFKA-15592 > URL: https://issues.apache.org/jira/browse/KAFKA-15592 > Project: Kafka > Issue Type: Sub-task > Components: clients, consumer >Reporter: Philip Nee >Assignee: Philip Nee >Priority: Major > Labels: kip-848, kip-848-client-support, kip-848-e2e, > kip-848-preview > Fix For: 3.7.0 > > > Currently, instantiating a membershipManager means the member will always > seek to join a group unless it has failed fatally. However, this is not > always the case because the member should be able to join and leave a group > any time during its life cycle. Maybe we should include an "inactive" state > in the state machine indicating the member does not want to be in a rebalance > group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15592) Member does not need to always try to join a group when a groupId is configured
[ https://issues.apache.org/jira/browse/KAFKA-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski updated KAFKA-15592: Fix Version/s: (was: 3.7.0) > Member does not need to always try to join a group when a groupId is > configured > --- > > Key: KAFKA-15592 > URL: https://issues.apache.org/jira/browse/KAFKA-15592 > Project: Kafka > Issue Type: Sub-task > Components: clients, consumer >Reporter: Philip Nee >Assignee: Philip Nee >Priority: Major > Labels: kip-848, kip-848-client-support, kip-848-e2e, > kip-848-preview > > Currently, instantiating a membershipManager means the member will always > seek to join a group unless it has failed fatally. However, this is not > always the case because the member should be able to join and leave a group > any time during its life cycle. Maybe we should include an "inactive" state > in the state machine indicating the member does not want to be in a rebalance > group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15592) Member does not need to always try to join a group when a groupId is configured
[ https://issues.apache.org/jira/browse/KAFKA-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15592: -- Fix Version/s: 3.7.0 > Member does not need to always try to join a group when a groupId is > configured > --- > > Key: KAFKA-15592 > URL: https://issues.apache.org/jira/browse/KAFKA-15592 > Project: Kafka > Issue Type: Sub-task > Components: clients, consumer >Reporter: Philip Nee >Assignee: Philip Nee >Priority: Major > Labels: kip-848, kip-848-client-support, kip-848-e2e, > kip-848-preview > Fix For: 3.7.0 > > > Currently, instantiating a membershipManager means the member will always > seek to join a group unless it has failed fatally. However, this is not > always the case because the member should be able to join and leave a group > any time during its life cycle. Maybe we should include an "inactive" state > in the state machine indicating the member does not want to be in a rebalance > group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15592) Member does not need to always try to join a group when a groupId is configured
[ https://issues.apache.org/jira/browse/KAFKA-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski updated KAFKA-15592: Fix Version/s: (was: 3.7.0) > Member does not need to always try to join a group when a groupId is > configured > --- > > Key: KAFKA-15592 > URL: https://issues.apache.org/jira/browse/KAFKA-15592 > Project: Kafka > Issue Type: Sub-task > Components: clients, consumer >Reporter: Philip Nee >Assignee: Philip Nee >Priority: Major > Labels: kip-848, kip-848-client-support, kip-848-e2e, > kip-848-preview > > Currently, instantiating a membershipManager means the member will always > seek to join a group unless it has failed fatally. However, this is not > always the case because the member should be able to join and leave a group > any time during its life cycle. Maybe we should include an "inactive" state > in the state machine indicating the member does not want to be in a rebalance > group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15592) Member does not need to always try to join a group when a groupId is configured
[ https://issues.apache.org/jira/browse/KAFKA-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15592: -- Fix Version/s: 3.7.0 > Member does not need to always try to join a group when a groupId is > configured > --- > > Key: KAFKA-15592 > URL: https://issues.apache.org/jira/browse/KAFKA-15592 > Project: Kafka > Issue Type: Sub-task > Components: clients, consumer >Reporter: Philip Nee >Assignee: Philip Nee >Priority: Major > Labels: kip-848, kip-848-client-support, kip-848-e2e, > kip-848-preview > Fix For: 3.7.0 > > > Currently, instantiating a membershipManager means the member will always > seek to join a group unless it has failed fatally. However, this is not > always the case because the member should be able to join and leave a group > any time during its life cycle. Maybe we should include an "inactive" state > in the state machine indicating the member does not want to be in a rebalance > group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15592) Member does not need to always try to join a group when a groupId is configured
[ https://issues.apache.org/jira/browse/KAFKA-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15592: -- Component/s: clients > Member does not need to always try to join a group when a groupId is > configured > --- > > Key: KAFKA-15592 > URL: https://issues.apache.org/jira/browse/KAFKA-15592 > Project: Kafka > Issue Type: Sub-task > Components: clients, consumer >Reporter: Philip Nee >Assignee: Philip Nee >Priority: Major > Labels: kip-848, kip-848-client-support, kip-848-e2e, > kip-848-preview > > Currently, instantiating a membershipManager means the member will always > seek to join a group unless it has failed fatally. However, this is not > always the case because the member should be able to join and leave a group > any time during its life cycle. Maybe we should include an "inactive" state > in the state machine indicating the member does not want to be in a rebalance > group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15592) Member does not need to always try to join a group when a groupId is configured
[ https://issues.apache.org/jira/browse/KAFKA-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Nee updated KAFKA-15592: --- Labels: kip-848 kip-848-client-support kip-848-e2e kip-848-preview (was: ) > Member does not need to always try to join a group when a groupId is > configured > --- > > Key: KAFKA-15592 > URL: https://issues.apache.org/jira/browse/KAFKA-15592 > Project: Kafka > Issue Type: Sub-task > Components: consumer >Reporter: Philip Nee >Assignee: Philip Nee >Priority: Major > Labels: kip-848, kip-848-client-support, kip-848-e2e, > kip-848-preview > > Currently, instantiating a membershipManager means the member will always > seek to join a group unless it has failed fatally. However, this is not > always the case because the member should be able to join and leave a group > any time during its life cycle. Maybe we should include an "inactive" state > in the state machine indicating the member does not want to be in a rebalance > group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15592) Member does not need to always try to join a group when a groupId is configured
[ https://issues.apache.org/jira/browse/KAFKA-15592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Nee updated KAFKA-15592: --- Parent: KAFKA-14048 Issue Type: Sub-task (was: Bug) > Member does not need to always try to join a group when a groupId is > configured > --- > > Key: KAFKA-15592 > URL: https://issues.apache.org/jira/browse/KAFKA-15592 > Project: Kafka > Issue Type: Sub-task > Components: consumer >Reporter: Philip Nee >Assignee: Philip Nee >Priority: Major > > Currently, instantiating a membershipManager means the member will always > seek to join a group unless it has failed fatally. However, this is not > always the case because the member should be able to join and leave a group > any time during its life cycle. Maybe we should include an "inactive" state > in the state machine indicating the member does not want to be in a rebalance > group. -- This message was sent by Atlassian Jira (v8.20.10#820010)