[jira] [Comment Edited] (KAFKA-6898) org.apache.kafka.common.errors.TimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490189#comment-16490189 ] huxihx edited comment on KAFKA-6898 at 5/25/18 3:58 AM: Could you check if the

[jira] [Commented] (KAFKA-6941) when passing port = 0 to worker, the advertisedPort still is 0 rather than a random port

[ https://issues.apache.org/jira/browse/KAFKA-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490114#comment-16490114 ] ASF GitHub Bot commented on KAFKA-6941: --- chia7712 opened a new pull request #5076: KAFKA-6941 when

[jira] [Commented] (KAFKA-6911) Incorrect check for keystore/truststore dynamic update

[ https://issues.apache.org/jira/browse/KAFKA-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489975#comment-16489975 ] ASF GitHub Bot commented on KAFKA-6911: --- hachikuji closed pull request #5029: KAFKA-6911: Fix

[jira] [Resolved] (KAFKA-6911) Incorrect check for keystore/truststore dynamic update

[ https://issues.apache.org/jira/browse/KAFKA-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6911. Resolution: Fixed > Incorrect check for keystore/truststore dynamic update >

[jira] [Commented] (KAFKA-6914) Kafka Connect - Plugins class should have a constructor that can take in parent ClassLoader

[ https://issues.apache.org/jira/browse/KAFKA-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489653#comment-16489653 ] Sriram KS commented on KAFKA-6914: -- [~ewencp] The case i have is I am building a Uber jar which contains

[jira] [Commented] (KAFKA-6813) Remove deprecated APIs from KIP-120 and KIP-182 in Streams

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

[jira] [Updated] (KAFKA-6946) Keep the session id for incremental fetch when fetch responses are throttled

[ https://issues.apache.org/jira/browse/KAFKA-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Lee updated KAFKA-6946: --- Summary: Keep the session id for incremental fetch when fetch responses are throttled (was: Keep the fetch

[jira] [Created] (KAFKA-6946) Keep the fetch session id for incremental fetch when

Jon Lee created KAFKA-6946: -- Summary: Keep the fetch session id for incremental fetch when Key: KAFKA-6946 URL: https://issues.apache.org/jira/browse/KAFKA-6946 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-6945) Add support to allow users to acquire delegation tokens for other users

Manikumar created KAFKA-6945: Summary: Add support to allow users to acquire delegation tokens for other users Key: KAFKA-6945 URL: https://issues.apache.org/jira/browse/KAFKA-6945 Project: Kafka

[jira] [Created] (KAFKA-6944) Add system tests testing the new throttling behavior using older clients/brokers

Jon Lee created KAFKA-6944: -- Summary: Add system tests testing the new throttling behavior using older clients/brokers Key: KAFKA-6944 URL: https://issues.apache.org/jira/browse/KAFKA-6944 Project: Kafka

[jira] [Commented] (KAFKA-4628) Support KTable/GlobalKTable Joins

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489493#comment-16489493 ] Guozhang Wang commented on KAFKA-4628: -- Hello Adam, Here is my estimate on the complexity:

[jira] [Updated] (KAFKA-4628) Support KTable/GlobalKTable Joins

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4628: - Labels: needs-kip (was: ) > Support KTable/GlobalKTable Joins >

[jira] [Commented] (KAFKA-6943) Have option to shutdown KS cleanly if any task crashes, or if all tasks crash

[ https://issues.apache.org/jira/browse/KAFKA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489485#comment-16489485 ] Guozhang Wang commented on KAFKA-6943: -- Hi Antony, for this feature request, what are the common

[jira] [Resolved] (KAFKA-6862) test toolchain

[ https://issues.apache.org/jira/browse/KAFKA-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6862. -- Resolution: Invalid Please reopen the Jira with more details. > test toolchain > -- > >

[jira] [Commented] (KAFKA-4217) KStream.transform equivalent of flatMap

[ https://issues.apache.org/jira/browse/KAFKA-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489444#comment-16489444 ] Matthias J. Sax commented on KAFKA-4217: Thanks for picking this up! Added you to the list of

[jira] [Assigned] (KAFKA-4217) KStream.transform equivalent of flatMap

[ https://issues.apache.org/jira/browse/KAFKA-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4217: -- Assignee: Bruno Cadonna > KStream.transform equivalent of flatMap >

[jira] [Updated] (KAFKA-6925) Memory leak in org.apache.kafka.streams.processor.internals.StreamThread$StreamsMetricsThreadImpl

[ https://issues.apache.org/jira/browse/KAFKA-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-6925: Description: *Note: this issue was fixed incidentally in 2.0, so it is only present in versions

[jira] [Assigned] (KAFKA-6925) Memory leak in org.apache.kafka.streams.processor.internals.StreamThread$StreamsMetricsThreadImpl

[ https://issues.apache.org/jira/browse/KAFKA-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-6925: --- Assignee: John Roesler > Memory leak in >

[jira] [Commented] (KAFKA-4217) KStream.transform equivalent of flatMap

[ https://issues.apache.org/jira/browse/KAFKA-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489401#comment-16489401 ] Bruno Cadonna commented on KAFKA-4217: -- I would like to work on this issue. Could somebody assign

[jira] [Commented] (KAFKA-6925) Memory leak in org.apache.kafka.streams.processor.internals.StreamThread$StreamsMetricsThreadImpl

[ https://issues.apache.org/jira/browse/KAFKA-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489252#comment-16489252 ] John Roesler commented on KAFKA-6925: - I read the ticket and took another look at parentSensors in

[jira] [Updated] (KAFKA-6940) Kafka Cluster and Zookeeper ensemble configuration with SASL authentication

[ https://issues.apache.org/jira/browse/KAFKA-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6940: - Component/s: (was: producer ) (was: log) (was:

[jira] [Created] (KAFKA-6942) Connect connectors api doesn't show versions of connectors

Antony Stubbs created KAFKA-6942: Summary: Connect connectors api doesn't show versions of connectors Key: KAFKA-6942 URL: https://issues.apache.org/jira/browse/KAFKA-6942 Project: Kafka

[jira] [Commented] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488998#comment-16488998 ] Ismael Juma commented on KAFKA-6762: This has been fixed in CP 4.1.1, please check the release notes.

[jira] [Resolved] (KAFKA-4505) Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4505. -- Resolution: Auto Closed {color:#00}Closing inactive issue. Please reopen if you think the issue

[jira] [Commented] (KAFKA-6616) kafka-merge-pr.py should use GitHub's REST API to merge

[ https://issues.apache.org/jira/browse/KAFKA-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488814#comment-16488814 ] Viktor Popov commented on KAFKA-6616: - [~ijuma], this one looks really interesting. May I start

[jira] [Resolved] (KAFKA-2036) Consumer and broker have different networks

[ https://issues.apache.org/jira/browse/KAFKA-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2036. -- Resolution: Duplicate Resolving this duplicate of KIP-235/KIP-302  > Consumer and broker have

[jira] [Commented] (KAFKA-6941) when passing port = 0 to worker, the advertisedPort still is 0 rather than a random port

[ https://issues.apache.org/jira/browse/KAFKA-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488767#comment-16488767 ] Chia-Ping Tsai commented on KAFKA-6941: --- BTW, the worker id base on the advertisedHost and 

[jira] [Resolved] (KAFKA-3793) Kafka Python Consumer library messages gets truncated

[ https://issues.apache.org/jira/browse/KAFKA-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3793. -- Resolution: Cannot Reproduce {color:#00}Closing inactive issue. Please reopen if you think the

[jira] [Commented] (KAFKA-6941) when passing port = 0 to worker, the advertisedPort still is 0 rather than a random port

[ https://issues.apache.org/jira/browse/KAFKA-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488758#comment-16488758 ] Chia-Ping Tsai commented on KAFKA-6941: --- I noticed this issue when building the mini connector

[jira] [Created] (KAFKA-6941) when passing port = 0 to worker, the advertisedPort still is 0 rather than a random port

Chia-Ping Tsai created KAFKA-6941: - Summary: when passing port = 0 to worker, the advertisedPort still is 0 rather than a random port Key: KAFKA-6941 URL: https://issues.apache.org/jira/browse/KAFKA-6941

[jira] [Commented] (KAFKA-5519) Support for multiple certificates in a single keystore

[ https://issues.apache.org/jira/browse/KAFKA-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488721#comment-16488721 ] sebastien diaz commented on KAFKA-5519: --- I m working for a future production with a centralized

[jira] [Comment Edited] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488588#comment-16488588 ] Uwe Eisele edited comment on KAFKA-6762 at 5/24/18 8:26 AM: After a restart of

[jira] [Comment Edited] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488588#comment-16488588 ] Uwe Eisele edited comment on KAFKA-6762 at 5/24/18 8:25 AM: After a restart of

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488628#comment-16488628 ] pradeep kumbhar commented on KAFKA-3410: Does the fix for KAFKA-1211 solves this issue? > Unclean

[jira] [Commented] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488588#comment-16488588 ] Uwe Eisele commented on KAFKA-6762: --- After a restart of the broker, log-cleaner thread runs in the same

[jira] [Updated] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ 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

[jira] [Commented] (KAFKA-6936) Scala API Wrapper for Streams uses default serializer for table aggregate

[ https://issues.apache.org/jira/browse/KAFKA-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488550#comment-16488550 ] Daniel Heinrich commented on KAFKA-6936: ah, didn't see that PR. Yes this will fix this issue. >

[jira] [Created] (KAFKA-6940) Kafka Cluster and Zookeeper ensemble configuration with SASL authentication

Shashank Jain created KAFKA-6940: Summary: Kafka Cluster and Zookeeper ensemble configuration with SASL authentication Key: KAFKA-6940 URL: https://issues.apache.org/jira/browse/KAFKA-6940 Project: