[jira] [Commented] (KAFKA-6617) Improve controller performance by batching reassignment znode write operation

[ https://issues.apache.org/jira/browse/KAFKA-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494694#comment-16494694 ] ASF GitHub Bot commented on KAFKA-6617: --- lindong28 closed pull request #4659: KAFKA-6617; Improve

[jira] [Commented] (KAFKA-6906) Kafka Streams does not commit transactions if data is produced via wall-clock punctuation

[ https://issues.apache.org/jira/browse/KAFKA-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494692#comment-16494692 ] Jagadesh Adireddi commented on KAFKA-6906: -- [~mjsax], should we keep using `commitOffsetNeeded` 

[jira] [Commented] (KAFKA-6776) Connect Rest Extension Plugin

[ https://issues.apache.org/jira/browse/KAFKA-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494673#comment-16494673 ] ASF GitHub Bot commented on KAFKA-6776: --- ewencp closed pull request #4931: KAFKA-6776 :

[jira] [Commented] (KAFKA-6953) [Streams] Schedulable KTable as Graph source (for minimizing aggregation pressure)

[ https://issues.apache.org/jira/browse/KAFKA-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494658#comment-16494658 ] Guozhang Wang commented on KAFKA-6953: -- Flavio, thanks for reporting your use case. On top of my

[jira] [Commented] (KAFKA-6967) TopologyTestDriver does not allow pre-populating state stores that have change logging

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

[jira] [Commented] (KAFKA-6783) consumer poll(timeout) blocked infinitely when no available bootstrap server

[ https://issues.apache.org/jira/browse/KAFKA-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494593#comment-16494593 ] ASF GitHub Bot commented on KAFKA-6783: --- koqizhao closed pull request #4861: KAFKA-6783: consumer

[jira] [Commented] (KAFKA-5664) Disable auto offset commit in ConsoleConsumer if no group is provided

[ https://issues.apache.org/jira/browse/KAFKA-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494502#comment-16494502 ] ASF GitHub Bot commented on KAFKA-5664: --- vahidhashemian closed pull request #3593: KAFKA-5664:

[jira] [Commented] (KAFKA-5812) Represent logDir with case class where absolute path is required

[ https://issues.apache.org/jira/browse/KAFKA-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494499#comment-16494499 ] ASF GitHub Bot commented on KAFKA-5812: --- lindong28 closed pull request #3763: KAFKA-5812; Represent

[jira] [Commented] (KAFKA-6913) Add primitive numeric converters to Connect

[ https://issues.apache.org/jira/browse/KAFKA-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494454#comment-16494454 ] ASF GitHub Bot commented on KAFKA-6913: --- ewencp closed pull request #5034: KAFKA-6913: Add Connect

[jira] [Commented] (KAFKA-5540) Deprecate and remove internal converter configs

[ https://issues.apache.org/jira/browse/KAFKA-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494443#comment-16494443 ] ASF GitHub Bot commented on KAFKA-5540: --- ewencp closed pull request #4693: KAFKA-5540: Deprecate

[jira] [Commented] (KAFKA-6906) Kafka Streams does not commit transactions if data is produced via wall-clock punctuation

[ https://issues.apache.org/jira/browse/KAFKA-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494307#comment-16494307 ] Matthias J. Sax commented on KAFKA-6906: [~jadireddi] no need to apologize :) >From my

[jira] [Commented] (KAFKA-6967) TopologyTestDriver does not allow pre-populating state stores that have change logging

[ https://issues.apache.org/jira/browse/KAFKA-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494299#comment-16494299 ] James Cheng commented on KAFKA-6967: If the very first call to the state store is a `store.put()`, it

[jira] [Updated] (KAFKA-6967) TopologyTestDriver does not allow pre-populating state stores that have change logging

[ https://issues.apache.org/jira/browse/KAFKA-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6967: --- Affects Version/s: 1.1.0 > TopologyTestDriver does not allow pre-populating state stores

[jira] [Updated] (KAFKA-6967) TopologyTestDriver does not allow pre-populating state stores that have change logging

[ https://issues.apache.org/jira/browse/KAFKA-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6967: --- Component/s: streams > TopologyTestDriver does not allow pre-populating state stores that

[jira] [Assigned] (KAFKA-6967) TopologyTestDriver does not allow pre-populating state stores that have change logging

[ https://issues.apache.org/jira/browse/KAFKA-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng reassigned KAFKA-6967: -- Assignee: Matthias J. Sax > TopologyTestDriver does not allow pre-populating state stores

[jira] [Created] (KAFKA-6967) TopologyTestDriver does not allow pre-populating state stores that have change logging

James Cheng created KAFKA-6967: -- Summary: TopologyTestDriver does not allow pre-populating state stores that have change logging Key: KAFKA-6967 URL: https://issues.apache.org/jira/browse/KAFKA-6967

[jira] [Created] (KAFKA-6966) Extend `TopologyDescription.Sink` to return `TopicNameExtractor`

Matthias J. Sax created KAFKA-6966: -- Summary: Extend `TopologyDescription.Sink` to return `TopicNameExtractor` Key: KAFKA-6966 URL: https://issues.apache.org/jira/browse/KAFKA-6966 Project: Kafka

[jira] [Updated] (KAFKA-6831) FileStreamSink is very slow

[ https://issues.apache.org/jira/browse/KAFKA-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6831: - Component/s: (was: consumer) > FileStreamSink is very slow > --- > >

[jira] [Updated] (KAFKA-6831) FileStreamSink is very slow

[ https://issues.apache.org/jira/browse/KAFKA-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6831: - Component/s: KafkaConnect > FileStreamSink is very slow > --- > >

[jira] [Resolved] (KAFKA-6831) FileStreamSink is very slow

[ https://issues.apache.org/jira/browse/KAFKA-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-6831. -- Resolution: Invalid Fix Version/s: (was: 1.1.0) [~vrmprabhat], first of all, these

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493976#comment-16493976 ] Jun Rao commented on KAFKA-3042: We fixed KAFKA-2729 in 1.1.0 that could lead to Cached zkVersion. >

[jira] [Updated] (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:all-tabpanel ] Randall Hauch updated KAFKA-6914: - Component/s: KafkaConnect > Kafka Connect - Plugins class should have a constructor that can

[jira] [Updated] (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:all-tabpanel ] Randall Hauch updated KAFKA-6914: - Issue Type: Improvement (was: Bug) > Kafka Connect - Plugins class should have a constructor

[jira] [Updated] (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:all-tabpanel ] Randall Hauch updated KAFKA-6914: - Priority: Minor (was: Major) > Kafka Connect - Plugins class should have a constructor that can

[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=16493942#comment-16493942 ] Ismael Juma commented on KAFKA-6965: Actually, what I said above is wrong. > log4j:WARN log messages

[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: Ismael Juma > log4j:WARN log messages printed when running kafka-console-producer

[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=16493904#comment-16493904 ] Ismael Juma commented on KAFKA-6965: Thanks for the report. I think it's just a matter of making the

[jira] [Updated] (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 updated KAFKA-6965: --- Labels: newbie (was: ) > log4j:WARN log messages printed when running kafka-console-producer OOB >

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

Yeva Byzek created KAFKA-6965: - Summary: log4j:WARN log messages printed when running kafka-console-producer OOB Key: KAFKA-6965 URL: https://issues.apache.org/jira/browse/KAFKA-6965 Project: Kafka

[jira] [Commented] (KAFKA-6717) TopicPartition Assined twice to a consumer group for 2 consumer instances

[ https://issues.apache.org/jira/browse/KAFKA-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493885#comment-16493885 ] Vahid Hashemian commented on KAFKA-6717: I ran a few tests using the Sticky Assignor (also with

[jira] [Commented] (KAFKA-6028) Improve the quota throttle communication.

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

[jira] [Closed] (KAFKA-6783) consumer poll(timeout) blocked infinitely when no available bootstrap server

[ https://issues.apache.org/jira/browse/KAFKA-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler closed KAFKA-6783. --- > consumer poll(timeout) blocked infinitely when no available bootstrap server >

[jira] [Resolved] (KAFKA-6783) consumer poll(timeout) blocked infinitely when no available bootstrap server

[ https://issues.apache.org/jira/browse/KAFKA-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-6783. - Resolution: Duplicate Hey [~koqizhao], We've merged

[jira] [Reopened] (KAFKA-5697) StreamThread.shutdown() need to interrupt the stream threads to break the loop

[ https://issues.apache.org/jira/browse/KAFKA-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reopened KAFKA-5697: - Assignee: John Roesler > StreamThread.shutdown() need to interrupt the stream threads to break

[jira] [Updated] (KAFKA-2651) Remove deprecated config alteration from TopicCommand in 0.9.1.0

[ https://issues.apache.org/jira/browse/KAFKA-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-2651: - Fix Version/s: (was: 2.0.0) > Remove deprecated config alteration from TopicCommand in 0.9.1.0 >

[jira] [Commented] (KAFKA-5905) Remove PrincipalBuilder and DefaultPrincipalBuilder

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

[jira] [Resolved] (KAFKA-6916) AdminClient does not refresh metadata on broker failure

[ https://issues.apache.org/jira/browse/KAFKA-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6916. Resolution: Fixed > AdminClient does not refresh metadata on broker failure >

[jira] [Commented] (KAFKA-6916) AdminClient does not refresh metadata on broker failure

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

[jira] [Commented] (KAFKA-5523) ReplayLogProducer not using the new Kafka consumer

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

[jira] [Commented] (KAFKA-6961) UnknownTopicOrPartitionException & NotLeaderForPartitionException upon replication of topics.

[ https://issues.apache.org/jira/browse/KAFKA-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493640#comment-16493640 ] praveen commented on KAFKA-6961: I am seeing similar log entry in non-leader broker's when creating

[jira] [Commented] (KAFKA-5523) ReplayLogProducer not using the new Kafka consumer

[ https://issues.apache.org/jira/browse/KAFKA-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493567#comment-16493567 ] Ismael Juma commented on KAFKA-5523: [~omkreddy], I agree that it's unclear why anyone would use this

[jira] [Created] (KAFKA-6964) Add ability to print all internal topic names

Bill Bejeck created KAFKA-6964: -- Summary: Add ability to print all internal topic names Key: KAFKA-6964 URL: https://issues.apache.org/jira/browse/KAFKA-6964 Project: Kafka Issue Type: New

[jira] [Commented] (KAFKA-5523) ReplayLogProducer not using the new Kafka consumer

[ https://issues.apache.org/jira/browse/KAFKA-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493552#comment-16493552 ] Manikumar commented on KAFKA-5523: -- [~ijuma] If we are going to retain this tool, I can work on this.

[jira] [Resolved] (KAFKA-2556) Corrupted index on log.dir updates

[ https://issues.apache.org/jira/browse/KAFKA-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2556. -- Resolution: Not A Problem Closing inactive issue. Kafka log.dir contains topic data and metadata

[jira] [Resolved] (KAFKA-3293) Consumers are not able to get messages.

[ https://issues.apache.org/jira/browse/KAFKA-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3293. -- Resolution: Cannot Reproduce Closing inactive issue. Please reopen if the issue still exists in newer

[jira] [Commented] (KAFKA-6933) Broker reports Corrupted index warnings apparently infinitely

[ https://issues.apache.org/jira/browse/KAFKA-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493317#comment-16493317 ] Franco Bonazza commented on KAFKA-6933: --- I think this is just a tuning issue, I've recovered the

[jira] [Commented] (KAFKA-6743) ConsumerPerformance fails to consume all messages on topics with large number of partitions

[ https://issues.apache.org/jira/browse/KAFKA-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493288#comment-16493288 ] Antony Stubbs commented on KAFKA-6743: -- Duplicate / relates to KAFKA-6225 > ConsumerPerformance

[jira] [Commented] (KAFKA-6961) UnknownTopicOrPartitionException & NotLeaderForPartitionException upon replication of topics.

[ https://issues.apache.org/jira/browse/KAFKA-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493167#comment-16493167 ] Manikumar commented on KAFKA-6961: -- Are you observing these error logs continuously? If they are only

[jira] [Updated] (KAFKA-6962) DescribeConfigsRequest Schema documentation is wrong/missing detail

[ https://issues.apache.org/jira/browse/KAFKA-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Policarpio updated KAFKA-6962: --- Description: The Resource fields for DescribeConfigsRequest for the following fields are all