[
https://issues.apache.org/jira/browse/KAFKA-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele resolved KAFKA-13003.
Resolution: Fixed
Pull Request #10935 has been merged.
> KafkaBroker advertises socket port inste
[
https://issues.apache.org/jira/browse/KAFKA-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370624#comment-17370624
]
Uwe Eisele edited comment on KAFKA-13003 at 6/28/21, 2:35 PM:
[
https://issues.apache.org/jira/browse/KAFKA-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370624#comment-17370624
]
Uwe Eisele commented on KAFKA-13003:
I create a pull request with a fix: https://git
Uwe Eisele created KAFKA-13003:
--
Summary: KafkaBroker advertises socket port instead of the
configured advertised port
Key: KAFKA-13003
URL: https://issues.apache.org/jira/browse/KAFKA-13003
Project: Kaf
[
https://issues.apache.org/jira/browse/KAFKA-12790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367691#comment-17367691
]
Uwe Eisele commented on KAFKA-12790:
There is also already a ticket for JDK 11 (KAFK
[
https://issues.apache.org/jira/browse/KAFKA-12786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367690#comment-17367690
]
Uwe Eisele commented on KAFKA-12786:
As of JDK 11.0.11, TLSv1.1 is disabled by defau
[
https://issues.apache.org/jira/browse/KAFKA-12790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367686#comment-17367686
]
Uwe Eisele edited comment on KAFKA-12790 at 6/22/21, 9:23 PM:
[
https://issues.apache.org/jira/browse/KAFKA-12790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367686#comment-17367686
]
Uwe Eisele edited comment on KAFKA-12790 at 6/22/21, 9:19 PM:
[
https://issues.apache.org/jira/browse/KAFKA-12790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367686#comment-17367686
]
Uwe Eisele commented on KAFKA-12790:
It looks like that the test also no longer runs
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488588#comment-16488588
]
Uwe Eisele edited comment on KAFKA-6762 at 5/24/18 8:26 AM:
Af
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488588#comment-16488588
]
Uwe Eisele edited comment on KAFKA-6762 at 5/24/18 8:25 AM:
Af
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488588#comment-16488588
]
Uwe Eisele commented on KAFKA-6762:
---
After a restart of the broker, log-cleaner thread r
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6762:
--
Attachment: __consumer_offsets-9_.tar.xz
> log-cleaner thread terminates due to java
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486975#comment-16486975
]
Uwe Eisele edited comment on KAFKA-6762 at 5/23/18 12:02 PM:
-
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486975#comment-16486975
]
Uwe Eisele edited comment on KAFKA-6762 at 5/23/18 10:25 AM:
-
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486975#comment-16486975
]
Uwe Eisele edited comment on KAFKA-6762 at 5/23/18 10:21 AM:
-
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486975#comment-16486975
]
Uwe Eisele edited comment on KAFKA-6762 at 5/23/18 10:19 AM:
-
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486975#comment-16486975
]
Uwe Eisele edited comment on KAFKA-6762 at 5/23/18 10:18 AM:
-
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486975#comment-16486975
]
Uwe Eisele edited comment on KAFKA-6762 at 5/23/18 10:16 AM:
-
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486975#comment-16486975
]
Uwe Eisele commented on KAFKA-6762:
---
We are experiencing the same problem. The log clean
[
https://issues.apache.org/jira/browse/KAFKA-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6715:
--
Description:
In our cluster we experienced a situation, in which the leader of all
partitions lead by t
[
https://issues.apache.org/jira/browse/KAFKA-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6715:
--
Description:
In our cluster we experienced a situation, in which the leader of all
partitions lead by t
[
https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6714:
--
Description:
In our Kafka cluster we experienced a situation in wich the Kafka controller
has all Broke
[
https://issues.apache.org/jira/browse/KAFKA-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6715:
--
Description:
In our cluster we experienced a situation, in which the leader of all
partitions lead by t
[
https://issues.apache.org/jira/browse/KAFKA-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6715:
--
Attachment: 20180319-1756_kafka01-jvm-stack.dump
> Leader transition for all partitions lead by two brok
Uwe Eisele created KAFKA-6715:
-
Summary: Leader transition for all partitions lead by two brokers
without visible reason
Key: KAFKA-6715
URL: https://issues.apache.org/jira/browse/KAFKA-6715
Project: Kafk
[
https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6714:
--
Environment: Kafka cluster on Amazon AWS EC2 r4.2xlarge instances with 5
nodes and a Zookeeper cluster o
[
https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6714:
--
Description:
In our Kafka cluster we experienced a situation in wich the Kafka controller
has all Broke
Uwe Eisele created KAFKA-6714:
-
Summary: KafkaController marks all Brokers as "Shutting down",
though only one broker has been shut down
Key: KAFKA-6714
URL: https://issues.apache.org/jira/browse/KAFKA-6714
[
https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6714:
--
Priority: Critical (was: Major)
> KafkaController marks all Brokers as "Shutting down", though only one
[
https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Eisele updated KAFKA-6714:
--
Description:
In our Kafka cluster we experienced a situation in wich the Kafka controller
has all Broke
31 matches
Mail list logo