[
https://issues.apache.org/jira/browse/KAFKA-15687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Wang updated KAFKA-15687:
----------------------------
Description:
We are trying to use static membership protocol for our consumers in
Kubernetes. When our pod was recreated, we found that the host address in the
group description will not change to the address of the new created pod.
For example we have one pod with *group.instance.id = id1 and ip = 192.168.0.1*
when the pod crashes, we will replace it with a new pod with same
*group.instance.id = id1* but a different {*}ip = 192.168.0.2{*}. After the new
pod joined in the consumer group, with the command "describe group", we found
the host is still {*}192.168.0.1{*}. This makes us cannot find correct consumer
instance when check the issue.
After read the source code, we found that the groupCoordinator will not change
the host address for the same {*}groupInstanceId{*}.
[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/coordinator/group/GroupMetadata.scala#L316]
Is it also possible to replace the host address when replace the static member?
was:
We are trying to using static membership protocol for our consumers in
Kubernetes. When our pod was recreated, we found that the host address in the
group description will not change to the address of the new created pod.
For example we have one pod with *group.instance.id = id1 and ip = 192.168.0.1*
when the pod crashes, we will replace it with a new pod with same
*group.instance.id = id1* but a different {*}ip = 192.168.0.2{*}. After the new
pod joined in the consumer group, with the command "describe group", we found
the host is still {*}192.168.0.1{*}. This makes us cannot find correct consumer
instance when check the issue.
After read the source code, we found that the groupCoordinator will not change
the host address for the same {*}groupInstanceId{*}.
[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/coordinator/group/GroupMetadata.scala#L316]
Is it also possible to replace the host address when replace the static member?
> Update host address for the GoupMetadata when replace static members
> --------------------------------------------------------------------
>
> Key: KAFKA-15687
> URL: https://issues.apache.org/jira/browse/KAFKA-15687
> Project: Kafka
> Issue Type: Improvement
> Components: group-coordinator
> Affects Versions: 3.6.0
> Reporter: Yu Wang
> Priority: Major
>
> We are trying to use static membership protocol for our consumers in
> Kubernetes. When our pod was recreated, we found that the host address in the
> group description will not change to the address of the new created pod.
> For example we have one pod with *group.instance.id = id1 and ip =
> 192.168.0.1* when the pod crashes, we will replace it with a new pod with
> same *group.instance.id = id1* but a different {*}ip = 192.168.0.2{*}. After
> the new pod joined in the consumer group, with the command "describe group",
> we found the host is still {*}192.168.0.1{*}. This makes us cannot find
> correct consumer instance when check the issue.
> After read the source code, we found that the groupCoordinator will not
> change the host address for the same {*}groupInstanceId{*}.
> [https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/coordinator/group/GroupMetadata.scala#L316]
> Is it also possible to replace the host address when replace the static
> member?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
