[jira] [Commented] (KAFKA-4869) 0.10.2.0 release notes incorrectly include KIP-115

[ https://issues.apache.org/jira/browse/KAFKA-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141283#comment-16141283 ] ASF GitHub Bot commented on KAFKA-4869: --- Github user asfgit closed the pull request

[jira] [Commented] (KAFKA-4869) 0.10.2.0 release notes incorrectly include KIP-115

[ https://issues.apache.org/jira/browse/KAFKA-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141278#comment-16141278 ] ASF GitHub Bot commented on KAFKA-4869: --- Github user ijuma commented on the issue:

[jira] [Comment Edited] (KAFKA-5779) Single message may exploit application based on KStream

[ https://issues.apache.org/jira/browse/KAFKA-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141251#comment-16141251 ] Seweryn Habdank-Wojewodzki edited comment on KAFKA-5779 at 8/25/17 6:22 AM:

[jira] [Commented] (KAFKA-5779) Single message may exploit application based on KStream

[ https://issues.apache.org/jira/browse/KAFKA-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141251#comment-16141251 ] Seweryn Habdank-Wojewodzki commented on KAFKA-5779: --- Hi Matthias, Thank

[jira] [Commented] (KAFKA-4691) ProducerInterceptor.onSend() is called after key and value are serialized

[ https://issues.apache.org/jira/browse/KAFKA-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141089#comment-16141089 ] Bill Bejeck commented on KAFKA-4691: [~francescolemma] are you still interested in doi

[jira] [Commented] (KAFKA-5233) Changes to punctuate semantics (KIP-138)

[ https://issues.apache.org/jira/browse/KAFKA-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140959#comment-16140959 ] Guozhang Wang commented on KAFKA-5233: -- [~mihbor] I have another pr for other related

[jira] [Commented] (KAFKA-5720) In Jenkins, kafka.api.SaslSslAdminClientIntegrationTest failed with org.apache.kafka.common.errors.TimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140923#comment-16140923 ] ASF GitHub Bot commented on KAFKA-5720: --- GitHub user cmccabe opened a pull request:

[jira] [Assigned] (KAFKA-5720) In Jenkins, kafka.api.SaslSslAdminClientIntegrationTest failed with org.apache.kafka.common.errors.TimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe reassigned KAFKA-5720: -- Assignee: Colin P. McCabe > In Jenkins, kafka.api.SaslSslAdminClientIntegrationTest fai

[jira] [Resolved] (KAFKA-5342) Distinguish abortable failures in transactional producer

[ https://issues.apache.org/jira/browse/KAFKA-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5342. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3716 [https://g

[jira] [Commented] (KAFKA-5342) Distinguish abortable failures in transactional producer

[ https://issues.apache.org/jira/browse/KAFKA-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140897#comment-16140897 ] ASF GitHub Bot commented on KAFKA-5342: --- Github user asfgit closed the pull request

[jira] [Created] (KAFKA-5784) Add a sensor for dropped records in window stores

Guozhang Wang created KAFKA-5784: Summary: Add a sensor for dropped records in window stores Key: KAFKA-5784 URL: https://issues.apache.org/jira/browse/KAFKA-5784 Project: Kafka Issue Type: B

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140862#comment-16140862 ] Ismael Juma commented on KAFKA-5780: Seems like most of the time is during LogManager.

[jira] [Comment Edited] (KAFKA-5771) org.apache.kafka.streams.state.internals.Segments#segments method returns incorrect results when segments were added out of order

[ https://issues.apache.org/jira/browse/KAFKA-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140853#comment-16140853 ] Guozhang Wang edited comment on KAFKA-5771 at 8/24/17 10:29 PM:

[jira] [Commented] (KAFKA-5771) org.apache.kafka.streams.state.internals.Segments#segments method returns incorrect results when segments were added out of order

[ https://issues.apache.org/jira/browse/KAFKA-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140853#comment-16140853 ] Guozhang Wang commented on KAFKA-5771: -- If I understands this correctly? This issue i

[jira] [Updated] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raoufeh Hashemian updated KAFKA-5780: - Attachment: shutdown.log shutdown_statechange.log shutdown_

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140844#comment-16140844 ] Raoufeh Hashemian commented on KAFKA-5780: -- Thanks [~apurva], I guess the size of

[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&focusedCommentId=16140832#comment-16140832 ] Guozhang Wang commented on KAFKA-4217: -- The issue with the current recommended {{forw

[jira] [Created] (KAFKA-5783) Implement KafkaPrincipalBuilder interface with support for SASL (KIP-189)

Jason Gustafson created KAFKA-5783: -- Summary: Implement KafkaPrincipalBuilder interface with support for SASL (KIP-189) Key: KAFKA-5783 URL: https://issues.apache.org/jira/browse/KAFKA-5783 Project:

[jira] [Comment Edited] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139966#comment-16139966 ] Murad M edited comment on KAFKA-5634 at 8/24/17 9:50 PM: - Figured

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140763#comment-16140763 ] Apurva Mehta commented on KAFKA-5780: - Let's try to focus on the CPU usage. In additio

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140754#comment-16140754 ] Apurva Mehta commented on KAFKA-5780: - Also, if the CPU remains high during shutdown,

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140707#comment-16140707 ] Apurva Mehta commented on KAFKA-5780: - Actually, looking at it further, the message be

[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&focusedCommentId=16140694#comment-16140694 ] Matthias J. Sax commented on KAFKA-4217: [~minfing] I guess this is TBD and should

[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&focusedCommentId=16140634#comment-16140634 ] Richard Yu commented on KAFKA-4217: --- Should only the original method signature be change

[jira] [Created] (KAFKA-5782) Avoid unnecessary PID reset when expire batches.

Jiangjie Qin created KAFKA-5782: --- Summary: Avoid unnecessary PID reset when expire batches. Key: KAFKA-5782 URL: https://issues.apache.org/jira/browse/KAFKA-5782 Project: Kafka Issue Type: Impr

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140526#comment-16140526 ] Apurva Mehta commented on KAFKA-5780: - When the controller is shutdown, it definitely

[jira] [Commented] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140422#comment-16140422 ] Apurva Mehta commented on KAFKA-5781: - If you don't collect jvm metrics, sharing the g

[jira] [Commented] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140416#comment-16140416 ] Apurva Mehta commented on KAFKA-5781: - Hi, do you also collect the JVM metrics for the

[jira] [Commented] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140402#comment-16140402 ] Jun Rao commented on KAFKA-5781: The metrics are described in http://kafka.apache.org/docu

[jira] [Updated] (KAFKA-5774) WorkerSinkTask failure exception should include cause

[ https://issues.apache.org/jira/browse/KAFKA-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5774: - Description: When the WorkerSinkTask shuts down because of a connector exception, the task throws

[jira] [Commented] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140386#comment-16140386 ] Raoufeh Hashemian commented on KAFKA-5781: -- Can you please guide me to the list o

[jira] [Assigned] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5780: --- Assignee: Apurva Mehta > Long shutdown time when updated to 0.11.0 >

[jira] [Commented] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140379#comment-16140379 ] Raoufeh Hashemian commented on KAFKA-5781: -- We upgraded the broker and producer i

[jira] [Resolved] (KAFKA-4350) Can't mirror from Kafka 0.9 to Kafka 0.10.1

[ https://issues.apache.org/jira/browse/KAFKA-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4350. -- Resolution: Won't Fix Closing as per comments. > Can't mirror from Kafka 0.9 to Kafka 0.10.1 >

[jira] [Resolved] (KAFKA-4109) kafka client send msg exception

[ https://issues.apache.org/jira/browse/KAFKA-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4109. -- Resolution: Cannot Reproduce Pl reopen if you think the issue still exists > kafka client send msg ex

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140315#comment-16140315 ] Raoufeh Hashemian commented on KAFKA-5780: -- I think I missed part of your last qu

[jira] [Resolved] (KAFKA-3885) Kafka new producer cannot failover

[ https://issues.apache.org/jira/browse/KAFKA-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3885. -- Resolution: Duplicate > Kafka new producer cannot failover > -- > >

[jira] [Commented] (KAFKA-5779) Single message may exploit application based on KStream

[ https://issues.apache.org/jira/browse/KAFKA-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140280#comment-16140280 ] Matthias J. Sax commented on KAFKA-5779: Kafka Streams can handle this, if you def

[jira] [Commented] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140278#comment-16140278 ] Jun Rao commented on KAFKA-5781: It would also be useful to know the producer latency brea

[jira] [Commented] (KAFKA-5603) Streams should not abort transaction when closing zombie task

[ https://issues.apache.org/jira/browse/KAFKA-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140268#comment-16140268 ] ASF GitHub Bot commented on KAFKA-5603: --- Github user mjsax closed the pull request a

[jira] [Commented] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140259#comment-16140259 ] Ismael Juma commented on KAFKA-5781: Just to double-check: the producers and brokers h

[jira] [Updated] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raoufeh Hashemian updated KAFKA-5781: - Description: When we upgraded from Kafka 0.10,2 to 0.11.0 , I started to see frequent thr

[jira] [Updated] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raoufeh Hashemian updated KAFKA-5781: - Description: When we upgraded from Kafka 0.10,2 to 0.11.0 , I started to see frequent thr

[jira] [Created] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

Raoufeh Hashemian created KAFKA-5781: Summary: Frequent long produce latency periods that result in reduced produce rate. Key: KAFKA-5781 URL: https://issues.apache.org/jira/browse/KAFKA-5781 Proj

[jira] [Resolved] (KAFKA-2414) Running kafka-producer-perf-test.sh with " --messages 10000000 --message-size 1000 --new-producer" will get WARN Error in I/O.

[ https://issues.apache.org/jira/browse/KAFKA-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2414. -- Resolution: Cannot Reproduce This might have been fixed in latest versions. Pl reopen if you think the

[jira] [Resolved] (KAFKA-2451) Exception logged but not managed

[ https://issues.apache.org/jira/browse/KAFKA-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2451. -- Resolution: Cannot Reproduce Pl reopen if you think the issue still exists > Exception logged but not

[jira] [Resolved] (KAFKA-2577) one node of Kafka cluster cannot process produce request

[ https://issues.apache.org/jira/browse/KAFKA-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2577. -- Resolution: Cannot Reproduce This might have fixed in latest versions. Pl reopen if you think the issue

[jira] [Resolved] (KAFKA-2560) Fatal error during KafkaServer startup because of Map failed error.

[ https://issues.apache.org/jira/browse/KAFKA-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2560. -- Resolution: Fixed This is due to java.lang.OutOfMemoryError. Pl reopen if you think the issue still ex

[jira] [Resolved] (KAFKA-2565) Offset Commit is not working if multiple consumers try to commit the offset

[ https://issues.apache.org/jira/browse/KAFKA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2565. -- Resolution: Cannot Reproduce may be related to deployment issue. Pl reopen if you think the issue still

[jira] [Resolved] (KAFKA-2829) Inconsistent naming in {Producer,Consumer} Callback interfaces

[ https://issues.apache.org/jira/browse/KAFKA-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2829. -- Resolution: Won't Fix These are public interfaces heavily used by users. It's not appropriate to change

[jira] [Resolved] (KAFKA-2966) 0.9.0 docs missing upgrade notes regarding replica lag

[ https://issues.apache.org/jira/browse/KAFKA-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2966. -- Resolution: Fixed > 0.9.0 docs missing upgrade notes regarding replica lag > ---

[jira] [Comment Edited] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140191#comment-16140191 ] Ismael Juma edited comment on KAFKA-5780 at 8/24/17 3:39 PM: -

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140191#comment-16140191 ] Ismael Juma commented on KAFKA-5780: I see, that's helpful. All brokers communicate wi

[jira] [Resolved] (KAFKA-627) Make UnknownTopicOrPartitionException a WARN in broker

[ https://issues.apache.org/jira/browse/KAFKA-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-627. - Resolution: Fixed Not observed on latest versions > Make UnknownTopicOrPartitionException a WARN in broker

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140173#comment-16140173 ] Raoufeh Hashemian commented on KAFKA-5780: -- broker 1002 is the same broker that i

[jira] [Resolved] (KAFKA-3332) Consumer can't consume messages from zookeeper chroot

[ https://issues.apache.org/jira/browse/KAFKA-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3332. -- Resolution: Cannot Reproduce > Consumer can't consume messages from zookeeper chroot > -

[jira] [Commented] (KAFKA-5749) Refactor SessionStore hierarchy

[ https://issues.apache.org/jira/browse/KAFKA-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140154#comment-16140154 ] ASF GitHub Bot commented on KAFKA-5749: --- GitHub user dguy opened a pull request:

[jira] [Resolved] (KAFKA-958) Please compile list of key metrics on the broker and client side and put it on a wiki

[ https://issues.apache.org/jira/browse/KAFKA-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-958. - Resolution: Fixed Key metrics are listed on monitoring section of Kafka documentation page > Please compi

[jira] [Comment Edited] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140123#comment-16140123 ] Ismael Juma edited comment on KAFKA-5780 at 8/24/17 2:56 PM: -

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140123#comment-16140123 ] Ismael Juma commented on KAFKA-5780: Also, one question: is broker 1002 unavailable? A

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140121#comment-16140121 ] Ismael Juma commented on KAFKA-5780: Something else that would help us fix this would

[jira] [Commented] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140117#comment-16140117 ] Ismael Juma commented on KAFKA-5780: [~RSH2000], can you please include the stacktrace

[jira] [Updated] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5780: --- Fix Version/s: 0.11.0.1 > Long shutdown time when updated to 0.11.0 >

[jira] [Updated] (KAFKA-5780) Long shutdown time when updated to 0.11.0

[ https://issues.apache.org/jira/browse/KAFKA-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raoufeh Hashemian updated KAFKA-5780: - Description: When we switched from Kafka 0.10.2 to Kafka 0.11.0 , We faced a problem with

[jira] [Resolved] (KAFKA-962) Add list topics to ClientUtils

[ https://issues.apache.org/jira/browse/KAFKA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-962. - Resolution: Fixed Topic management methods are added to new admin client. > Add list topics to ClientUtils

[jira] [Resolved] (KAFKA-1339) Time based offset retrieval seems broken

[ https://issues.apache.org/jira/browse/KAFKA-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1339. -- Resolution: Fixed Time-based offset retrieval is improved with the introduction of message timestamp.

[jira] [Created] (KAFKA-5780) Long shutdown time when updated to 0.11.0

Raoufeh Hashemian created KAFKA-5780: Summary: Long shutdown time when updated to 0.11.0 Key: KAFKA-5780 URL: https://issues.apache.org/jira/browse/KAFKA-5780 Project: Kafka Issue Type: B

[jira] [Resolved] (KAFKA-1497) Change producer load-balancing algorithm in MirrorMaker

[ https://issues.apache.org/jira/browse/KAFKA-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1497. -- Resolution: Fixed MIrrorMaker now uses single producer instance. > Change producer load-balancing algor

[jira] [Commented] (KAFKA-5726) KafkaConsumer.subscribe() overload that takes just Pattern without ConsumerRebalanceListener

[ https://issues.apache.org/jira/browse/KAFKA-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140050#comment-16140050 ] Attila Kreiner commented on KAFKA-5726: --- Created [KIP|https://cwiki.apache.org/conf

[jira] [Commented] (KAFKA-5769) Transient test failure org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperationsWithZeroSizedCache

[ https://issues.apache.org/jira/browse/KAFKA-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139974#comment-16139974 ] ASF GitHub Bot commented on KAFKA-5769: --- Github user dguy closed the pull request at

[jira] [Commented] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139966#comment-16139966 ] Murad M commented on KAFKA-5634: Any workaround that can be used to get over this situatio

[jira] [Resolved] (KAFKA-4425) Topic created with CreateTopic command, does not list partitions in metadata

[ https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4425. -- Resolution: Not A Problem Fixed as per [~Fristi] comments > Topic created with CreateTopic command, doe

[jira] [Commented] (KAFKA-4869) 0.10.2.0 release notes incorrectly include KIP-115

[ https://issues.apache.org/jira/browse/KAFKA-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139935#comment-16139935 ] ASF GitHub Bot commented on KAFKA-4869: --- Github user omkreddy commented on the issue

[jira] [Commented] (KAFKA-4869) 0.10.2.0 release notes incorrectly include KIP-115

[ https://issues.apache.org/jira/browse/KAFKA-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139934#comment-16139934 ] ASF GitHub Bot commented on KAFKA-4869: --- GitHub user omkreddy opened a pull request:

[jira] [Commented] (KAFKA-1324) Debian packaging

[ https://issues.apache.org/jira/browse/KAFKA-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139931#comment-16139931 ] Martin Schröder commented on KAFKA-1324: bq. I think we can leave packaging out of

[jira] [Commented] (KAFKA-5754) Refactor Streams to use LogContext

[ https://issues.apache.org/jira/browse/KAFKA-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139784#comment-16139784 ] ASF GitHub Bot commented on KAFKA-5754: --- GitHub user umesh9794 opened a pull request

[jira] [Commented] (KAFKA-5771) org.apache.kafka.streams.state.internals.Segments#segments method returns incorrect results when segments were added out of order

[ https://issues.apache.org/jira/browse/KAFKA-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139767#comment-16139767 ] Alexander Radzishevsky commented on KAFKA-5771: --- See application below: {co

[jira] [Created] (KAFKA-5779) Single message may exploit application based on KStream

Seweryn Habdank-Wojewodzki created KAFKA-5779: - Summary: Single message may exploit application based on KStream Key: KAFKA-5779 URL: https://issues.apache.org/jira/browse/KAFKA-5779 Projec