[jira] [Comment Edited] (KAFKA-5810) Improve authentication logging on the broker-side

[ https://issues.apache.org/jira/browse/KAFKA-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497701#comment-16497701 ] Gérald Quintana edited comment on KAFKA-5810 at 6/1/18 8:10 AM: In order

[jira] [Commented] (KAFKA-5810) Improve authentication logging on the broker-side

[ https://issues.apache.org/jira/browse/KAFKA-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497701#comment-16497701 ] Gérald Quintana commented on KAFKA-5810: In order to be able to detect security attacks, I'd like

[jira] [Commented] (KAFKA-6979) Add max.block.ms to consumer for default timeout behavior

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

[jira] [Updated] (KAFKA-6982) java.lang.ArithmeticException: / by zero

[ https://issues.apache.org/jira/browse/KAFKA-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wade wu updated KAFKA-6982: --- Description: Producer keeps sending messages to Kafka, Kafka is down.  Server.log shows:  ..

[jira] [Created] (KAFKA-6982) java.lang.ArithmeticException: / by zero

wade wu created KAFKA-6982: -- Summary: java.lang.ArithmeticException: / by zero Key: KAFKA-6982 URL: https://issues.apache.org/jira/browse/KAFKA-6982 Project: Kafka Issue Type: Bug

[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=16498741#comment-16498741 ] Ted Yu commented on KAFKA-4628: --- [~abellemare]: Would you start a KIP for this enhancement ? Thanks >

[jira] [Created] (KAFKA-6983) Error while deleting segments - The process cannot access the file because it is being used by another process

wade wu created KAFKA-6983: -- Summary: Error while deleting segments - The process cannot access the file because it is being used by another process Key: KAFKA-6983 URL: https://issues.apache.org/jira/browse/KAFKA-6983

[jira] [Commented] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498733#comment-16498733 ] Guozhang Wang commented on KAFKA-6860: -- Thanks for the detailed explanation of the issue. I looked

[jira] [Commented] (KAFKA-6981) Missing Connector Config (errors.deadletterqueue.topic.name) kills Connect Clusters

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

[jira] [Updated] (KAFKA-6981) Missing Connector Config (errors.deadletterqueue.topic.name) kills Connect Clusters

[ https://issues.apache.org/jira/browse/KAFKA-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Satish updated KAFKA-6981: Description: The trunk version of AK currently tries to incorrectly read the property 

[jira] [Commented] (KAFKA-6822) Kafka Consumer 0.10.2.1 can not normally read data from Kafka 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498734#comment-16498734 ] Guozhang Wang commented on KAFKA-6822: -- cc [~mjsax] > Kafka Consumer 0.10.2.1 can not normally read

[jira] [Commented] (KAFKA-6965) log4j:WARN log messages printed when running kafka-console-producer OOB

[ https://issues.apache.org/jira/browse/KAFKA-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498745#comment-16498745 ] Yeva Byzek commented on KAFKA-6965: --- Correct, please close this issue. Details: This issue was a

[jira] [Resolved] (KAFKA-6965) log4j:WARN log messages printed when running kafka-console-producer OOB

[ https://issues.apache.org/jira/browse/KAFKA-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6965. Resolution: Not A Bug > log4j:WARN log messages printed when running kafka-console-producer OOB >

[jira] [Commented] (KAFKA-6982) java.lang.ArithmeticException: / by zero

[ https://issues.apache.org/jira/browse/KAFKA-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498824#comment-16498824 ] huxihx commented on KAFKA-6982: --- Did you resize the processor thread pool? >

[jira] [Commented] (KAFKA-6870) Concurrency conflicts in SampledStat

[ https://issues.apache.org/jira/browse/KAFKA-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498412#comment-16498412 ] Kevin Lafferty commented on KAFKA-6870: --- This depends on

[jira] [Assigned] (KAFKA-6965) log4j:WARN log messages printed when running kafka-console-producer OOB

[ https://issues.apache.org/jira/browse/KAFKA-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-6965: -- Assignee: (was: Ismael Juma) > log4j:WARN log messages printed when running

[jira] [Commented] (KAFKA-6965) log4j:WARN log messages printed when running kafka-console-producer OOB

[ https://issues.apache.org/jira/browse/KAFKA-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498690#comment-16498690 ] Ismael Juma commented on KAFKA-6965: I think [~yevabyzek] said that this was not an issue after all.

[jira] [Commented] (KAFKA-6938) Add documentation for accessing Headers on Kafka Streams Processor API

[ https://issues.apache.org/jira/browse/KAFKA-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498724#comment-16498724 ] Guozhang Wang commented on KAFKA-6938: -- [~jeqo] are you actively working on this JIRA? We are

[jira] [Updated] (KAFKA-6981) Missing Connector Config (errors.deadletterqueue.topic.name) kills Connect Clusters

[ https://issues.apache.org/jira/browse/KAFKA-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Satish updated KAFKA-6981: Priority: Major (was: Minor) > Missing Connector Config (errors.deadletterqueue.topic.name) kills

[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=16498492#comment-16498492 ] ASF GitHub Bot commented on KAFKA-6925: --- vvcephei opened a new pull request #5119: KAFKA-6925: fix

[jira] [Created] (KAFKA-6981) Missing Connector Config (errors.deadletterqueue.topic.name) kills Connect Clusters

Arjun Satish created KAFKA-6981: --- Summary: Missing Connector Config (errors.deadletterqueue.topic.name) kills Connect Clusters Key: KAFKA-6981 URL: https://issues.apache.org/jira/browse/KAFKA-6981

[jira] [Assigned] (KAFKA-6098) Delete and Re-create topic operation could result in race condition

[ https://issues.apache.org/jira/browse/KAFKA-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah reassigned KAFKA-6098: --- Assignee: Dhruvil Shah > Delete and Re-create topic operation could result in race

[jira] [Commented] (KAFKA-6977) Kafka Streams - java.lang.IllegalStateException: Unexpected error code 2 while fetching data

[ https://issues.apache.org/jira/browse/KAFKA-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498723#comment-16498723 ] Guozhang Wang commented on KAFKA-6977: -- cc [~mjsax] > Kafka Streams -

[jira] [Resolved] (KAFKA-6760) responses not logged properly in controller

[ https://issues.apache.org/jira/browse/KAFKA-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6760. Resolution: Fixed Fix Version/s: 1.1.1 2.0.0 > responses not logged

[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=16498565#comment-16498565 ] ASF GitHub Bot commented on KAFKA-6925: --- guozhangwang closed pull request #5119: KAFKA-6925: fix

[jira] [Commented] (KAFKA-6760) responses not logged properly in controller

[ https://issues.apache.org/jira/browse/KAFKA-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498714#comment-16498714 ] ASF GitHub Bot commented on KAFKA-6760: --- ijuma closed pull request #4834: KAFKA-6760: Responses not

[jira] [Commented] (KAFKA-6959) Any impact we foresee if we upgrade Linux version or move to VM instead of physical Linux server

[ https://issues.apache.org/jira/browse/KAFKA-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497840#comment-16497840 ] Manikumar commented on KAFKA-6959: -- Post these kind of queries to us...@kafka.apache.org mailing list

[jira] [Resolved] (KAFKA-3743) kafka-server-start.sh: Unhelpful error message

[ https://issues.apache.org/jira/browse/KAFKA-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3743. -- Resolution: Duplicate > kafka-server-start.sh: Unhelpful error message >

[jira] [Updated] (KAFKA-6335) SimpleAclAuthorizerTest#testHighConcurrencyModificationOfResourceAcls fails intermittently

[ https://issues.apache.org/jira/browse/KAFKA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-6335: - Fix Version/s: (was: 2.0.0) > SimpleAclAuthorizerTest#testHighConcurrencyModificationOfResourceAcls

[jira] [Assigned] (KAFKA-6972) Kafka ACL does not work expected with wildcard

[ https://issues.apache.org/jira/browse/KAFKA-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau reassigned KAFKA-6972: --- Assignee: Sönke Liebau > Kafka ACL does not work expected with wildcard >

[jira] [Commented] (KAFKA-6309) add support for getting topic defaults from AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498033#comment-16498033 ] Manikumar commented on KAFKA-6309: -- This functionality is supported in

[jira] [Commented] (KAFKA-6973) setting invalid timestamp causes Kafka broker restart to fail

[ https://issues.apache.org/jira/browse/KAFKA-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498044#comment-16498044 ] ASF GitHub Bot commented on KAFKA-6973: --- ijuma closed pull request #5106: KAFKA-6973: TopicCommand

[jira] [Resolved] (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:all-tabpanel ] Guozhang Wang resolved KAFKA-6936. -- Resolution: Fixed Fix Version/s: 2.0.0 > Scala API Wrapper for Streams uses default

[jira] [Resolved] (KAFKA-6581) ConsumerGroupCommand hangs if even one of the partition is unavailable

[ https://issues.apache.org/jira/browse/KAFKA-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6581. -- Resolution: Fixed Fix Version/s: (was: 0.10.0.2) 2.0.0 This is addressed

[jira] [Resolved] (KAFKA-3899) Consumer.poll() stuck in loop if wrong credentials are supplied

[ https://issues.apache.org/jira/browse/KAFKA-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3899. -- Resolution: Fixed Assignee: (was: Edoardo Comar) Fix Version/s: 2.0.0 This is

[jira] [Resolved] (KAFKA-6973) setting invalid timestamp causes Kafka broker restart to fail

[ https://issues.apache.org/jira/browse/KAFKA-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6973. Resolution: Fixed Fix Version/s: 2.0.0 > setting invalid timestamp causes Kafka broker

[jira] [Updated] (KAFKA-6973) setting invalid timestamp causes Kafka broker restart to fail

[ https://issues.apache.org/jira/browse/KAFKA-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6973: --- Priority: Major (was: Critical) > setting invalid timestamp causes Kafka broker restart to fail >

[jira] [Resolved] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3177. -- Resolution: Fixed This is addressed by KIP-266. > Kafka consumer can hang when position() is called

[jira] [Resolved] (KAFKA-3727) Consumer.poll() stuck in loop on non-existent topic manually assigned

[ https://issues.apache.org/jira/browse/KAFKA-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3727. -- Resolution: Fixed This is addressed by KIP-266. > Consumer.poll() stuck in loop on non-existent topic

[jira] [Created] (KAFKA-6980) Recommended MaxDirectMemorySize for consumers

John Lu created KAFKA-6980: -- Summary: Recommended MaxDirectMemorySize for consumers Key: KAFKA-6980 URL: https://issues.apache.org/jira/browse/KAFKA-6980 Project: Kafka Issue Type: Wish

[jira] [Resolved] (KAFKA-3503) Throw exception on missing/non-existent partition

[ https://issues.apache.org/jira/browse/KAFKA-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3503. -- Resolution: Duplicate > Throw exception on missing/non-existent partition >

[jira] [Resolved] (KAFKA-3011) Consumer.poll(0) blocks if Kafka not accessible

[ https://issues.apache.org/jira/browse/KAFKA-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3011. -- Resolution: Fixed This is addressed by KIP-266.  > Consumer.poll(0) blocks if Kafka not accessible >

[jira] [Resolved] (KAFKA-4571) Consumer fails to retrieve messages if started before producer

[ https://issues.apache.org/jira/browse/KAFKA-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4571. -- Resolution: Auto Closed Closing inactive issue. Please reopen if the issue still exists. > Consumer

[jira] [Resolved] (KAFKA-5304) Kafka Producer throwing infinite NullPointerExceptions

[ https://issues.apache.org/jira/browse/KAFKA-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5304. -- Resolution: Auto Closed Closing inactive issue. Please reopen if the issue still exists. > Kafka

[jira] [Resolved] (KAFKA-3822) Kafka Consumer close() hangs indefinitely if Kafka Broker shutdown while connected

[ https://issues.apache.org/jira/browse/KAFKA-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3822. -- Resolution: Fixed This is addressed by KIP-266.  > Kafka Consumer close() hangs indefinitely if Kafka

[jira] [Resolved] (KAFKA-3457) KafkaConsumer.committed(...) hangs forever if port number is wrong

[ https://issues.apache.org/jira/browse/KAFKA-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3457. -- Resolution: Fixed This is addressed by KIP-266.  > KafkaConsumer.committed(...) hangs forever if port

[jira] [Resolved] (KAFKA-4751) kafka-clients-0.9.0.2.4.2.11-1 issue not throwing exception.

[ https://issues.apache.org/jira/browse/KAFKA-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4751. -- Resolution: Fixed This is addressed by KIP-266.  > kafka-clients-0.9.0.2.4.2.11-1 issue not throwing

[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=16498202#comment-16498202 ] ASF GitHub Bot commented on KAFKA-6925: --- guozhangwang closed pull request #5108: KAFKA-6925: fix

[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 ] Guozhang Wang updated KAFKA-6925: - Fix Version/s: 1.1.1 > Memory leak in >

[jira] [Commented] (KAFKA-6207) Include start of record when RecordIsTooLarge

[ https://issues.apache.org/jira/browse/KAFKA-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498297#comment-16498297 ] Tadhg Pearson commented on KAFKA-6207: -- [~ewencp] - any feedback on this? > Include start of record

[jira] [Resolved] (KAFKA-5424) KafkaConsumer.listTopics() throws Exception when unauthorized topics exist in cluster

[ https://issues.apache.org/jira/browse/KAFKA-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5424. -- Resolution: Fixed This has been fixed via KAFKA-3396 > KafkaConsumer.listTopics() throws Exception