[jira] [Resolved] (KAFKA-7115) InMemoryKeyValueLoggedStore does not flush the changelog

[ https://issues.apache.org/jira/browse/KAFKA-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hashan Gayasri Udugahapattuwa resolved KAFKA-7115. -- Resolution: Not A Problem This the expected behaviour > InMemo

[jira] [Commented] (KAFKA-7115) InMemoryKeyValueLoggedStore does not flush the changelog

[ https://issues.apache.org/jira/browse/KAFKA-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527241#comment-16527241 ] Hashan Gayasri Udugahapattuwa commented on KAFKA-7115: -- [~guozhang]

[jira] [Updated] (KAFKA-7118) Make KafkaConsumer compatible with multiple threads

[ https://issues.apache.org/jira/browse/KAFKA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-7118: -- Description: It was discovered that there is a performance constraint relating to {{KafkaConsumer#close

[jira] [Updated] (KAFKA-7118) Make KafkaConsumer compatible with multiple threads

[ https://issues.apache.org/jira/browse/KAFKA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-7118: -- Summary: Make KafkaConsumer compatible with multiple threads (was: KafkaConsumer#close() is not thread

[jira] [Updated] (KAFKA-6836) Upgrade metrics library

[ https://issues.apache.org/jira/browse/KAFKA-6836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6836: --- Fix Version/s: (was: 1.1.2) > Upgrade metrics library > --- > >

[jira] [Updated] (KAFKA-5975) No response when deleting topics and delete.topic.enable=false

[ https://issues.apache.org/jira/browse/KAFKA-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5975: --- Fix Version/s: (was: 1.1.2) 2.1.0 > No response when deleting topics and delet

[jira] [Updated] (KAFKA-7104) ReplicaFetcher thread may die because of inconsistent log start offset in fetch response

[ https://issues.apache.org/jira/browse/KAFKA-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7104: --- Fix Version/s: (was: 1.1.2) 1.1.1 > ReplicaFetcher thread may die because of i

[jira] [Updated] (KAFKA-6780) log cleaner shouldn't clean messages beyond high watermark

[ https://issues.apache.org/jira/browse/KAFKA-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6780: --- Fix Version/s: (was: 1.1.2) > log cleaner shouldn't clean messages beyond high watermark > --

[jira] [Updated] (KAFKA-6809) connections-created metric does not behave as expected

[ https://issues.apache.org/jira/browse/KAFKA-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-6809: --- Fix Version/s: (was: 1.1.2) 1.1.1 > connections-created metric does not behave

[jira] [Updated] (KAFKA-7091) AdminClient should handle FindCoordinatorResponse errors

[ https://issues.apache.org/jira/browse/KAFKA-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7091: --- Fix Version/s: (was: 2.0.1) 2.0.0 > AdminClient should handle FindCoordinatorR

[jira] [Updated] (KAFKA-7059) Offer new constructor on ProducerRecord

[ https://issues.apache.org/jira/browse/KAFKA-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7059: --- Fix Version/s: (was: 2.0.1) > Offer new constructor on ProducerRecord >

[jira] [Updated] (KAFKA-7082) Concurrent createTopics calls may throw NodeExistsException

[ https://issues.apache.org/jira/browse/KAFKA-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7082: --- Fix Version/s: (was: 1.1.2) (was: 2.0.1) 1.1.1

[jira] [Updated] (KAFKA-7076) Broker startup could be inefficient when using old message format

[ https://issues.apache.org/jira/browse/KAFKA-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7076: --- Fix Version/s: (was: 2.0.1) 2.0.0 > Broker startup could be inefficient when u

[jira] [Commented] (KAFKA-7113) AdminClient.create has an infinite retry loop bug

[ https://issues.apache.org/jira/browse/KAFKA-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527185#comment-16527185 ] 02tmqrmje9 commented on KAFKA-7113: --- It's not ideal but it would be workable in the sen

[jira] [Commented] (KAFKA-7111) Review the NetworkClient log level used

[ https://issues.apache.org/jira/browse/KAFKA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527136#comment-16527136 ] Luan Cestari commented on KAFKA-7111: - Hi Stanislav, Sorry, I worked until very late

[jira] [Updated] (KAFKA-7118) KafkaConsumer#close() is not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-7118: -- Component/s: consumer > KafkaConsumer#close() is not thread safe >

[jira] [Updated] (KAFKA-7118) KafkaConsumer#close() is not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-7118: -- Description: It was discovered that there is a potential problem relating to {{KafkaConsumer#close()}}.

[jira] [Updated] (KAFKA-7118) KafkaConsumer#close() is not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-7118: -- Summary: KafkaConsumer#close() is not thread safe (was: Currently, it was discovered that KafkaConsume

[jira] [Created] (KAFKA-7118) Currently, it was discovered that KafkaConsumer's close() method might not be multi-thread safe when multiple cores are calling the same consumer.

Richard Yu created KAFKA-7118: - Summary: Currently, it was discovered that KafkaConsumer's close() method might not be multi-thread safe when multiple cores are calling the same consumer. Key: KAFKA-7118 URL: https:

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

[ https://issues.apache.org/jira/browse/KAFKA-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Lee resolved KAFKA-6944. Resolution: Fixed > Add system tests testing the new throttling behavior using older > clients/brokers > -

[jira] [Assigned] (KAFKA-6039) Improve TaskAssignor to be more load balanced

[ https://issues.apache.org/jira/browse/KAFKA-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-6039: Assignee: (was: Bill Bejeck) > Improve TaskAssignor to be more load balanced > ---

[jira] [Assigned] (KAFKA-6039) Improve TaskAssignor to be more load balanced

[ https://issues.apache.org/jira/browse/KAFKA-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-6039: Assignee: Bill Bejeck > Improve TaskAssignor to be more load balanced > --

[jira] [Updated] (KAFKA-4969) State-store workload-aware StreamsPartitionAssignor

[ https://issues.apache.org/jira/browse/KAFKA-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4969: - Fix Version/s: 1.1.0 > State-store workload-aware StreamsPartitionAssignor >

[jira] [Commented] (KAFKA-7028) super.users doesn't work with custom principals

[ https://issues.apache.org/jira/browse/KAFKA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526922#comment-16526922 ] Jason Gustafson commented on KAFKA-7028: >From KIP-189, the intention was to alwa

[jira] [Commented] (KAFKA-7115) InMemoryKeyValueLoggedStore does not flush the changelog

[ https://issues.apache.org/jira/browse/KAFKA-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526902#comment-16526902 ] Guozhang Wang commented on KAFKA-7115: -- [~hashan] The underlying RecordCollector is

[jira] [Comment Edited] (KAFKA-7110) Windowed changelog keys not deserialized properly by TimeWindowedSerde

[ https://issues.apache.org/jira/browse/KAFKA-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526857#comment-16526857 ] Guozhang Wang edited comment on KAFKA-7110 at 6/28/18 10:39 PM: ---

[jira] [Commented] (KAFKA-7110) Windowed changelog keys not deserialized properly by TimeWindowedSerde

[ https://issues.apache.org/jira/browse/KAFKA-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526860#comment-16526860 ] Shawn Nguyen commented on KAFKA-7110: - 1) If we want the changelog to use toBinary, i

[jira] [Commented] (KAFKA-7110) Windowed changelog keys not deserialized properly by TimeWindowedSerde

[ https://issues.apache.org/jira/browse/KAFKA-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526857#comment-16526857 ] Guozhang Wang commented on KAFKA-7110: -- 1) Not sure I understand your statement.. We

[jira] [Resolved] (KAFKA-7097) VerifiableProducer does not work properly with --message-create-time argument

[ https://issues.apache.org/jira/browse/KAFKA-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7097. -- Resolution: Fixed Assignee: Ted Yu Reviewer: Guozhang Wang Fix Version/

[jira] [Commented] (KAFKA-7097) VerifiableProducer does not work properly with --message-create-time argument

[ https://issues.apache.org/jira/browse/KAFKA-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526814#comment-16526814 ] ASF GitHub Bot commented on KAFKA-7097: --- guozhangwang closed pull request #5292: KA

[jira] [Assigned] (KAFKA-6788) Grouping consumer requests per consumer coordinator in admin client

[ https://issues.apache.org/jira/browse/KAFKA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shun Guan reassigned KAFKA-6788: Assignee: Shun Guan > Grouping consumer requests per consumer coordinator in admin client > --

[jira] [Commented] (KAFKA-6177) kafka-mirror-maker.sh RecordTooLargeException

[ https://issues.apache.org/jira/browse/KAFKA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526730#comment-16526730 ] jason wang commented on KAFKA-6177: --- Hi Ted, The original poster (Remi) was using 0.10

[jira] [Commented] (KAFKA-6460) Add mocks for state stores used in Streams unit testing

[ https://issues.apache.org/jira/browse/KAFKA-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526697#comment-16526697 ] Shun Guan commented on KAFKA-6460: -- Is this still needs to be work on? Thanks. > Add mo

[jira] [Created] (KAFKA-7117) Allow AclCommand to use AdminClient API

Manikumar created KAFKA-7117: Summary: Allow AclCommand to use AdminClient API Key: KAFKA-7117 URL: https://issues.apache.org/jira/browse/KAFKA-7117 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-6969) AdminClient should provide a way to get the version of a node

[ https://issues.apache.org/jira/browse/KAFKA-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526644#comment-16526644 ] Charly Molter commented on KAFKA-6969: -- It’s not an issue for say but it would be a

[jira] [Commented] (KAFKA-7110) Windowed changelog keys not deserialized properly by TimeWindowedSerde

[ https://issues.apache.org/jira/browse/KAFKA-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526643#comment-16526643 ] Shawn Nguyen commented on KAFKA-7110: - Thanks for the quick response [~guozhang]. 1)

[jira] [Commented] (KAFKA-7112) StreamThread does not check for state again after pollRequests()

[ https://issues.apache.org/jira/browse/KAFKA-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526581#comment-16526581 ] ASF GitHub Bot commented on KAFKA-7112: --- guozhangwang closed pull request #5306: KA

[jira] [Resolved] (KAFKA-7116) Provide separate SSL configs for Kafka Broker replication

[ https://issues.apache.org/jira/browse/KAFKA-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani resolved KAFKA-7116. --- Resolution: Implemented Thanks [~ijuma] > Provide separate SSL configs for K

[jira] [Commented] (KAFKA-7116) Provide separate SSL configs for Kafka Broker replication

[ https://issues.apache.org/jira/browse/KAFKA-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526512#comment-16526512 ] Ismael Juma commented on KAFKA-7116: This is possible today by using listener name ov

[jira] [Created] (KAFKA-7116) Provide separate SSL configs for Kafka Broker replication

Sriharsha Chintalapani created KAFKA-7116: - Summary: Provide separate SSL configs for Kafka Broker replication Key: KAFKA-7116 URL: https://issues.apache.org/jira/browse/KAFKA-7116 Project: Kaf

[jira] [Commented] (KAFKA-6968) Call RebalanceListener in MockConsumer

[ https://issues.apache.org/jira/browse/KAFKA-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526492#comment-16526492 ] Andras Beni commented on KAFKA-6968: [~bgummalla] As I can see in [current code|htt

[jira] [Commented] (KAFKA-6788) Grouping consumer requests per consumer coordinator in admin client

[ https://issues.apache.org/jira/browse/KAFKA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526483#comment-16526483 ] Shun Guan commented on KAFKA-6788: -- Is this still needs to be work on? Thanks. > Groupi

[jira] [Commented] (KAFKA-7106) Remove segment/segmentInterval from Window definition

[ https://issues.apache.org/jira/browse/KAFKA-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526451#comment-16526451 ] John Roesler commented on KAFKA-7106: - Just preserving a comment from Guozhang: {quot

[jira] [Commented] (KAFKA-7112) StreamThread does not check for state again after pollRequests()

[ https://issues.apache.org/jira/browse/KAFKA-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526446#comment-16526446 ] Guozhang Wang commented on KAFKA-7112: -- I think so, would chat to release manager [~

[jira] [Commented] (KAFKA-6621) Update Streams docs with details for UncaughtExceptionHandler

[ https://issues.apache.org/jira/browse/KAFKA-6621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526416#comment-16526416 ] Matthias J. Sax commented on KAFKA-6621: Ticket is not resolved, so yes, it's sti

[jira] [Commented] (KAFKA-7108) "Exactly-once" stream breaks production exception handler contract

[ https://issues.apache.org/jira/browse/KAFKA-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526414#comment-16526414 ] Matthias J. Sax commented on KAFKA-7108: The retry config is strange. Can you sha

[jira] [Commented] (KAFKA-7111) Review the NetworkClient log level used

[ https://issues.apache.org/jira/browse/KAFKA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526405#comment-16526405 ] Stanislav Kozlovski commented on KAFKA-7111: [~lcestari] I followed the instr

[jira] [Commented] (KAFKA-6992) Configuring the batch.size to zero won't disable the batching entirely

[ https://issues.apache.org/jira/browse/KAFKA-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526404#comment-16526404 ] Chia-Ping Tsai commented on KAFKA-6992: --- {quote}Hi, does this need to be worked on?

[jira] [Commented] (KAFKA-6621) Update Streams docs with details for UncaughtExceptionHandler

[ https://issues.apache.org/jira/browse/KAFKA-6621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526396#comment-16526396 ] Bhagya Lakshmi Gummalla commented on KAFKA-6621: [~mjsax] Hi, is this sti

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

[ https://issues.apache.org/jira/browse/KAFKA-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526392#comment-16526392 ] Bhagya Lakshmi Gummalla commented on KAFKA-6980: [~jlu717] Hi, does this

[jira] [Commented] (KAFKA-6992) Configuring the batch.size to zero won't disable the batching entirely

[ https://issues.apache.org/jira/browse/KAFKA-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526391#comment-16526391 ] Bhagya Lakshmi Gummalla commented on KAFKA-6992: [~chia7712] Hi, does thi

[jira] [Commented] (KAFKA-7090) Zookeeper client setting in server-properties

[ https://issues.apache.org/jira/browse/KAFKA-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526390#comment-16526390 ] Manikumar commented on KAFKA-7090: -- Kafka still uses Zookeeper 3.4 client dependency. Cu

[jira] [Commented] (KAFKA-6939) Change the default of log.message.timestamp.difference.max.ms to 500 years

[ https://issues.apache.org/jira/browse/KAFKA-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526388#comment-16526388 ] Bhagya Lakshmi Gummalla commented on KAFKA-6939: [~badai] Is this still a

[jira] [Commented] (KAFKA-6968) Call RebalanceListener in MockConsumer

[ https://issues.apache.org/jira/browse/KAFKA-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526384#comment-16526384 ] Bhagya Lakshmi Gummalla commented on KAFKA-6968: [~andrasbeni] Is this st

[jira] [Commented] (KAFKA-6969) AdminClient should provide a way to get the version of a node

[ https://issues.apache.org/jira/browse/KAFKA-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526382#comment-16526382 ] Bhagya Lakshmi Gummalla commented on KAFKA-6969: [~cmolter] Is this still

[jira] [Commented] (KAFKA-7090) Zookeeper client setting in server-properties

[ https://issues.apache.org/jira/browse/KAFKA-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526372#comment-16526372 ] Bhagya Lakshmi Gummalla commented on KAFKA-7090: [~ctr] Can you please te

[jira] [Resolved] (KAFKA-6809) connections-created metric does not behave as expected

[ https://issues.apache.org/jira/browse/KAFKA-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-6809. --- Resolution: Fixed Reviewer: Rajini Sivaram Fix Version/s: (was: 2.1.0)

[jira] [Commented] (KAFKA-7111) Review the NetworkClient log level used

[ https://issues.apache.org/jira/browse/KAFKA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526258#comment-16526258 ] Stanislav Kozlovski commented on KAFKA-7111: Okay [~lcestari], I will look in

[jira] [Commented] (KAFKA-7111) Review the NetworkClient log level used

[ https://issues.apache.org/jira/browse/KAFKA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526251#comment-16526251 ] Luan Cestari commented on KAFKA-7111: - Hi, I used the docker images from https://git

[jira] [Commented] (KAFKA-7034) Remove the duplicated listTopics from Consumer

[ https://issues.apache.org/jira/browse/KAFKA-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526215#comment-16526215 ] Manikumar commented on KAFKA-7034: -- AdminClient.listTopics() gives the topic names and C

[jira] [Created] (KAFKA-7115) InMemoryKeyValueLoggedStore does not flush the changelog

Hashan Gayasri Udugahapattuwa created KAFKA-7115: Summary: InMemoryKeyValueLoggedStore does not flush the changelog Key: KAFKA-7115 URL: https://issues.apache.org/jira/browse/KAFKA-7115

[jira] [Commented] (KAFKA-7111) Review the NetworkClient log level used

[ https://issues.apache.org/jira/browse/KAFKA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526213#comment-16526213 ] Stanislav Kozlovski commented on KAFKA-7111: [~lcestari] how can I reproduce

[jira] [Commented] (KAFKA-6268) Tools should now swallow exceptions like resolving network names

[ https://issues.apache.org/jira/browse/KAFKA-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526212#comment-16526212 ] Stanislav Kozlovski commented on KAFKA-6268: I could not reproduce this with

[jira] [Resolved] (KAFKA-7099) KafkaLog4jAppender - not sending any message with level DEBUG

[ https://issues.apache.org/jira/browse/KAFKA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7099. -- Resolution: Duplicate Resolving this as duplicate of  KAFKA-6415.  Please post your observation/ssolut

[jira] [Comment Edited] (KAFKA-7099) KafkaLog4jAppender - not sending any message with level DEBUG

[ https://issues.apache.org/jira/browse/KAFKA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526195#comment-16526195 ] Manikumar edited comment on KAFKA-7099 at 6/28/18 10:29 AM: R

[jira] [Created] (KAFKA-7114) Kafka Not sending few partitions messages to consumers

Gnanasoundari created KAFKA-7114: Summary: Kafka Not sending few partitions messages to consumers Key: KAFKA-7114 URL: https://issues.apache.org/jira/browse/KAFKA-7114 Project: Kafka Issue Ty

[jira] [Comment Edited] (KAFKA-7108) "Exactly-once" stream breaks production exception handler contract

[ https://issues.apache.org/jira/browse/KAFKA-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525977#comment-16525977 ] Anna O edited comment on KAFKA-7108 at 6/28/18 8:06 AM: [~mjsax] 

[jira] [Assigned] (KAFKA-7111) Review the NetworkClient log level used

[ https://issues.apache.org/jira/browse/KAFKA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-7111: - Assignee: Stanislav Kozlovski This looks similar to KAFKA-6268 > Review the NetworkClie

[jira] [Commented] (KAFKA-6177) kafka-mirror-maker.sh RecordTooLargeException

[ https://issues.apache.org/jira/browse/KAFKA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526015#comment-16526015 ] Ted Yu commented on KAFKA-6177: --- I searched server.properties attached to the JIRA but didn