[jira] [Updated] (KAFKA-7625) Kafka Broker node JVM crash - kafka.coordinator.transaction.TransactionCoordinator.$anonfun$handleEndTransaction

[ https://issues.apache.org/jira/browse/KAFKA-7625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Puzoń updated KAFKA-7625: --- Attachment: hs_err_pid20124.log hs_err_pid19405.log

[jira] [Commented] (KAFKA-7625) Kafka Broker node JVM crash - kafka.coordinator.transaction.TransactionCoordinator.$anonfun$handleEndTransaction

[ https://issues.apache.org/jira/browse/KAFKA-7625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720980#comment-16720980 ] Sebastian Puzoń commented on KAFKA-7625: It was stable for 10 days, attached 3 dumps. > Kafka

[jira] [Commented] (KAFKA-7690) Change disk allocation policy for multiple partitions on a broker when topic is created

[ https://issues.apache.org/jira/browse/KAFKA-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720917#comment-16720917 ] haiyangyu commented on KAFKA-7690: -- [~huxi_2b] when create topic or add partition, there is a situation

[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720876#comment-16720876 ] Dong Lin commented on KAFKA-7297: - [~junrao] Ah I would not be able to work on this. Is this an urgent

[jira] [Assigned] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-7297: --- Assignee: Zhanxiang (Patrick) Huang (was: Dong Lin) > Both read/write access to Log.segments

[jira] [Updated] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7297: Reporter: Dong Lin (was: Zhanxiang (Patrick) Huang) > Both read/write access to Log.segments should be

[jira] [Updated] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7297: Reporter: Zhanxiang (Patrick) Huang (was: Dong Lin) > Both read/write access to Log.segments should be

[jira] [Commented] (KAFKA-7690) Change disk allocation policy for multiple partitions on a broker when topic is created

[ https://issues.apache.org/jira/browse/KAFKA-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720867#comment-16720867 ] huxihx commented on KAFKA-7690: --- I did not understand the strategy you proposed here. Do you mean a

[jira] [Commented] (KAFKA-7732) Kafka broker lag metrics is more than 0, but no partitions are under replicated

[ https://issues.apache.org/jira/browse/KAFKA-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720846#comment-16720846 ] huxihx commented on KAFKA-7732: --- It's already fixed in KAFKA-7704. > Kafka broker lag metrics is more than

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720819#comment-16720819 ] Jun Rao commented on KAFKA-2729: [~murri71], my earlier comment was referring to that we fixed the

[jira] [Assigned] (KAFKA-7734) Metrics tags should use LinkedHashMap to guarantee ordering

[ https://issues.apache.org/jira/browse/KAFKA-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu reassigned KAFKA-7734: Assignee: lambdaliu > Metrics tags should use LinkedHashMap to guarantee ordering >

[jira] [Updated] (KAFKA-7572) Producer should not send requests with negative partition id

[ https://issues.apache.org/jira/browse/KAFKA-7572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaodong Yang updated KAFKA-7572: Reviewer: Guozhang Wang (was: Jun Rao) > Producer should not send requests with negative

[jira] [Updated] (KAFKA-7572) Producer should not send requests with negative partition id

[ https://issues.apache.org/jira/browse/KAFKA-7572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaodong Yang updated KAFKA-7572: Flags: Patch,Important (was: Patch) Labels: patch-available (was: ) > Producer should not

[jira] [Updated] (KAFKA-7572) Producer should not send requests with negative partition id

[ https://issues.apache.org/jira/browse/KAFKA-7572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaodong Yang updated KAFKA-7572: Flags: Patch Affects Version/s: 1.1.1 > Producer should not send requests with

[jira] [Created] (KAFKA-7734) Metrics tags should use LinkedHashMap to guarantee ordering

Guozhang Wang created KAFKA-7734: Summary: Metrics tags should use LinkedHashMap to guarantee ordering Key: KAFKA-7734 URL: https://issues.apache.org/jira/browse/KAFKA-7734 Project: Kafka

[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720710#comment-16720710 ] Jun Rao commented on KAFKA-7297: To follow up on that, another related issue is that currently, we are

[jira] [Resolved] (KAFKA-5335) Controller should batch updatePartitionReassignmentData() operation

[ https://issues.apache.org/jira/browse/KAFKA-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-5335. - Resolution: Won't Do > Controller should batch updatePartitionReassignmentData() operation >

[jira] [Commented] (KAFKA-1714) more better bootstrapping of the gradle-wrapper.jar

[ https://issues.apache.org/jira/browse/KAFKA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720454#comment-16720454 ] ASF GitHub Bot commented on KAFKA-1714: --- granthenke opened a new pull request #6031: KAFKA-1714:

[jira] [Assigned] (KAFKA-1714) more better bootstrapping of the gradle-wrapper.jar

[ https://issues.apache.org/jira/browse/KAFKA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-1714: -- Assignee: Grant Henke > more better bootstrapping of the gradle-wrapper.jar >

[jira] [Resolved] (KAFKA-2124) gradlew is not working on a fresh checkout

[ https://issues.apache.org/jira/browse/KAFKA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-2124. Resolution: Duplicate Assignee: Grant Henke > gradlew is not working on a fresh checkout >

[jira] [Commented] (KAFKA-7733) MockConsumer doesn't respect reset strategy

[ https://issues.apache.org/jira/browse/KAFKA-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720419#comment-16720419 ] ASF GitHub Bot commented on KAFKA-7733: --- srdo opened a new pull request #6030: KAFKA-7733: Reset

[jira] [Resolved] (KAFKA-7655) Metadata spamming requests from Kafka Streams under some circumstances, potential DOS

[ https://issues.apache.org/jira/browse/KAFKA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7655. Resolution: Fixed Fix Version/s: 2.0.2 2.1.1

[jira] [Created] (KAFKA-7733) MockConsumer doesn't respect reset strategy

Stig Rohde Døssing created KAFKA-7733: - Summary: MockConsumer doesn't respect reset strategy Key: KAFKA-7733 URL: https://issues.apache.org/jira/browse/KAFKA-7733 Project: Kafka Issue

[jira] [Commented] (KAFKA-7655) Metadata spamming requests from Kafka Streams under some circumstances, potential DOS

[ https://issues.apache.org/jira/browse/KAFKA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720370#comment-16720370 ] Matthias J. Sax commented on KAFKA-7655: Added you to the list on contributors and assigned the

[jira] [Assigned] (KAFKA-7655) Metadata spamming requests from Kafka Streams under some circumstances, potential DOS

[ https://issues.apache.org/jira/browse/KAFKA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-7655: -- Assignee: Pasquale Vazzana > Metadata spamming requests from Kafka Streams under some

[jira] [Assigned] (KAFKA-7631) NullPointerException when SCRAM is allowed bu ScramLoginModule is not in broker's jaas.conf

[ https://issues.apache.org/jira/browse/KAFKA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Sasvari reassigned KAFKA-7631: - Assignee: Viktor Somogyi (was: Attila Sasvari) > NullPointerException when SCRAM is

[jira] [Created] (KAFKA-7732) Kafka broker lag metrics is more than 0, but no partitions are under replicated

Mathias Kub created KAFKA-7732: -- Summary: Kafka broker lag metrics is more than 0, but no partitions are under replicated Key: KAFKA-7732 URL: https://issues.apache.org/jira/browse/KAFKA-7732 Project:

[jira] [Commented] (KAFKA-7655) Metadata spamming requests from Kafka Streams under some circumstances, potential DOS

[ https://issues.apache.org/jira/browse/KAFKA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720316#comment-16720316 ] ASF GitHub Bot commented on KAFKA-7655: --- mjsax closed pull request #5929: KAFKA-7655 Metadata

[jira] [Created] (KAFKA-7731) JMX metrics for client connections: how many, what version, what language, source ip etc...

Antony Stubbs created KAFKA-7731: Summary: JMX metrics for client connections: how many, what version, what language, source ip etc... Key: KAFKA-7731 URL: https://issues.apache.org/jira/browse/KAFKA-7731

[jira] [Updated] (KAFKA-7731) JMX metrics from the broker for client connections: how many, what version, what language, source ip etc...

[ https://issues.apache.org/jira/browse/KAFKA-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antony Stubbs updated KAFKA-7731: - Summary: JMX metrics from the broker for client connections: how many, what version, what

[jira] [Commented] (KAFKA-7729) Mysterious disk increase when switching to RedHat OpenJDK

[ https://issues.apache.org/jira/browse/KAFKA-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720146#comment-16720146 ] Dimitris Mandalidis commented on KAFKA-7729: nvm found it (KAFKA-6828) > Mysterious disk

[jira] [Commented] (KAFKA-7729) Mysterious disk increase when switching to RedHat OpenJDK

[ https://issues.apache.org/jira/browse/KAFKA-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720114#comment-16720114 ] Dimitris Mandalidis commented on KAFKA-7729: Thanks [~ijuma], do you know if there's an issue

[jira] [Commented] (KAFKA-7729) Mysterious disk increase when switching to RedHat OpenJDK

[ https://issues.apache.org/jira/browse/KAFKA-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720078#comment-16720078 ] Ismael Juma commented on KAFKA-7729: There is a regression in some versions of Java where sparse

[jira] [Created] (KAFKA-7730) Limit total number of active connections in the broker

Rajini Sivaram created KAFKA-7730: - Summary: Limit total number of active connections in the broker Key: KAFKA-7730 URL: https://issues.apache.org/jira/browse/KAFKA-7730 Project: Kafka Issue

[jira] [Created] (KAFKA-7729) Mysterious disk increase when switching to RedHat OpenJDK

Dimitris Mandalidis created KAFKA-7729: -- Summary: Mysterious disk increase when switching to RedHat OpenJDK Key: KAFKA-7729 URL: https://issues.apache.org/jira/browse/KAFKA-7729 Project: Kafka