You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Alexandre Dupriez (Jira)" <ji...@apache.org> on 2020/03/20 17:06:00 UTC
[jira] [Comment Edited] (KAFKA-7958) Transactions are broken with
kubernetes hosted brokers
[ https://issues.apache.org/jira/browse/KAFKA-7958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063526#comment-17063526 ]
Alexandre Dupriez edited comment on KAFKA-7958 at 3/20/20, 5:05 PM:
--------------------------------------------------------------------
_"Would be good to get confirmation though.":_ confirmed the fix for [[KAFKA-7755||#KAFKA-7755]https://issues.apache.org/jira/browse/KAFKA-7755 []|#KAFKA-7755] fixes the problem in the transaction manager. Tested on 2.2.1.
was (Author: hangleton):
_"Would be good to get confirmation though.":_ confirmed the fix for [#KAFKA-7755] fixes the problem in the transaction manager. Tested on 2.2.1.
> Transactions are broken with kubernetes hosted brokers
> ------------------------------------------------------
>
> Key: KAFKA-7958
> URL: https://issues.apache.org/jira/browse/KAFKA-7958
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.1.0
> Environment: cp-kakfka 2.1.1-1, kafka-streams 2.1.1
> Reporter: Thomas Dickinson
> Priority: Major
>
> After a rolling re-start in a kubernetes-like environment, brokers may change IP address. From our logs it seems that the transaction manager in the brokers never re-resolves the DNS name of other brokers, keeping stale pod IPs. Thus transactions stop working.
> ??[2019-02-20 02:20:20,085] WARN [TransactionCoordinator id=1001] Connection to node 0 (khaki-joey-kafka-0.khaki-joey-kafka-headless.hyperspace-dev/[10.233.124.181:9092|http://10.233.124.181:9092/]) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)??
> ??[2019-02-20 02:20:57,205] WARN [TransactionCoordinator id=1001] Connection to node 1 (khaki-joey-kafka-1.khaki-joey-kafka-headless.hyperspace-dev/[10.233.122.67:9092|http://10.233.122.67:9092/]) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)??
> This is from the log from broker 1001 which was restarted first, followed by 1 and then 0. The log entries are from the day after the rolling restart.
> I note a similar issue was fixed for clients 2.1.1 https://issues.apache.org/jira/browse/KAFKA-7755. We are using streams lib 2.1.1
> *Update* We are now testing with Kafka 2.1.1 (docker cp-kafka 5.1.2-1) and it looks like this may be resolved. Would be good to get confirmation though.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)