[
https://issues.apache.org/jira/browse/KAFKA-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190370#comment-17190370
]
Jennifer Thompson commented on KAFKA-10428:
---
Setting
{{"header.converter":
Jennifer Thompson created KAFKA-10428:
-
Summary: Mirror Maker connect applies base64 encoding to string
headers
Key: KAFKA-10428
URL: https://issues.apache.org/jira/browse/KAFKA-10428
Project:
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jennifer Thompson resolved KAFKA-7845.
--
Resolution: Fixed
Fix Version/s: 2.1.1
> Kafka clients do not re-resolve ips
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777502#comment-16777502
]
Jennifer Thompson commented on KAFKA-7845:
--
We just deployed Kafka 2.1.1 (Confluent 5.1.2), and
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765577#comment-16765577
]
Jennifer Thompson edited comment on KAFKA-7845 at 2/12/19 1:07 AM:
---
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765577#comment-16765577
]
Jennifer Thompson commented on KAFKA-7845:
--
Quite probably. I tried using the 2.1.1-rc1 snapshot
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jennifer Thompson updated KAFKA-7845:
-
Description:
When one of our Kafka brokers dies and a new one replaces it (via an aws
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jennifer Thompson updated KAFKA-7845:
-
Description:
When one of our Kafka brokers dies and a new one replaces it (via an aws
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jennifer Thompson updated KAFKA-7845:
-
Description:
When one of our Kafka brokers dies and a new one replaces it (via an aws
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jennifer Thompson updated KAFKA-7845:
-
Description:
When one of our Kafka brokers dies and a new one replaces it (via an aws
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jennifer Thompson updated KAFKA-7845:
-
Description:
When one of our Kafka brokers dies and a new one replaces it (via an aws
[
https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jennifer Thompson updated KAFKA-7845:
-
Summary: Kafka clients do not re-resolve ips when a broker is replaced.
(was:
Jennifer Thompson created KAFKA-7845:
Summary: NotLeaderForPartitionException error when publishing
after a broker has died
Key: KAFKA-7845
URL: https://issues.apache.org/jira/browse/KAFKA-7845
[
https://issues.apache.org/jira/browse/KAFKA-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459102#comment-16459102
]
Jennifer Thompson commented on KAFKA-6390:
--
That issue (ZOOKEEPER-2960) should be fixed in 3.4.12
14 matches
Mail list logo