[jira] [Created] (KAFKA-7207) Make rate & total metrics documentation consistent

Kevin Lu created KAFKA-7207: --- Summary: Make rate & total metrics documentation consistent Key: KAFKA-7207 URL: https://issues.apache.org/jira/browse/KAFKA-7207 Project: Kafka Issue Type:

[jira] [Comment Edited] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556767#comment-16556767 ] Harjit Singh edited comment on KAFKA-6520 at 7/26/18 3:01 AM: -- Pardon my

[jira] [Commented] (KAFKA-6014) new consumer mirror maker halts after committing offsets to a deleted topic

[ https://issues.apache.org/jira/browse/KAFKA-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556804#comment-16556804 ] Felix GV commented on KAFKA-6014: - What is the behavior of MM given this change? Does it retry (i.e.:

[jira] [Commented] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556767#comment-16556767 ] Harjit Singh commented on KAFKA-6520: - Pardon my ignorance. I'mm trying to get my feet wet with the

[jira] [Comment Edited] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556767#comment-16556767 ] Harjit Singh edited comment on KAFKA-6520 at 7/26/18 1:46 AM: -- Pardon my

[jira] [Commented] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556757#comment-16556757 ] Matthias J. Sax commented on KAFKA-6520: [~harjitdotsingh] If you want to work on this ticket,

[jira] [Commented] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556479#comment-16556479 ] Harjit Singh commented on KAFKA-6520: - I didn't see the proposed options.   I have figured out

[jira] [Assigned] (KAFKA-6639) Follower may have sparse index if catching up

[ https://issues.apache.org/jira/browse/KAFKA-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Barrett reassigned KAFKA-6639: -- Assignee: Bob Barrett > Follower may have sparse index if catching up >

[jira] [Commented] (KAFKA-6817) UnknownProducerIdException when writing messages with old timestamps

[ https://issues.apache.org/jira/browse/KAFKA-6817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556415#comment-16556415 ] Matthias J. Sax commented on KAFKA-6817: If you hit KAFKA-7190 you would observe similar

[jira] [Issue Comment Deleted] (KAFKA-6817) UnknownProducerIdException when writing messages with old timestamps

[ https://issues.apache.org/jira/browse/KAFKA-6817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6817: --- Comment: was deleted (was: Maybe you hit KAFKA-7190 ?) > UnknownProducerIdException when

[jira] [Commented] (KAFKA-6817) UnknownProducerIdException when writing messages with old timestamps

[ https://issues.apache.org/jira/browse/KAFKA-6817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556414#comment-16556414 ] Matthias J. Sax commented on KAFKA-6817: Maybe you hit KAFKA-7190 ? > UnknownProducerIdException

[jira] [Commented] (KAFKA-6817) UnknownProducerIdException when writing messages with old timestamps

[ https://issues.apache.org/jira/browse/KAFKA-6817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556411#comment-16556411 ] Collin Scangarella commented on KAFKA-6817: --- [~mjsax] are there any other conditions which

[jira] [Assigned] (KAFKA-6639) Follower may have sparse index if catching up

[ https://issues.apache.org/jira/browse/KAFKA-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah reassigned KAFKA-6639: --- Assignee: (was: Dhruvil Shah) > Follower may have sparse index if catching up >

[jira] [Resolved] (KAFKA-6014) new consumer mirror maker halts after committing offsets to a deleted topic

[ https://issues.apache.org/jira/browse/KAFKA-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6014. Resolution: Resolved We changed the behavior of the consumer in KAFKA-6829 so that unknown

[jira] [Assigned] (KAFKA-6635) Producer close does not await pending transaction

[ https://issues.apache.org/jira/browse/KAFKA-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-6635: -- Assignee: (was: Jason Gustafson) > Producer close does not await pending

[jira] [Updated] (KAFKA-7206) Enable batching in FindCoordinator

[ https://issues.apache.org/jira/browse/KAFKA-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yishun Guan updated KAFKA-7206: --- Description: To quote [~guozhang] : "The proposal is that, we extend FindCoordinatorRequest to have

[jira] [Updated] (KAFKA-7206) Enable batching in FindCoordinator

[ https://issues.apache.org/jira/browse/KAFKA-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yishun Guan updated KAFKA-7206: --- Labels: needs-discussion needs-kip newbie++ (was: newbie++) > Enable batching in FindCoordinator >

[jira] [Updated] (KAFKA-7206) Enable batching in FindCoordinator

[ https://issues.apache.org/jira/browse/KAFKA-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yishun Guan updated KAFKA-7206: --- Description: To quote [~guozhang] : "The proposal is that, we extend FindCoordinatorRequest to have

[jira] [Updated] (KAFKA-7206) Enable batching in FindCoordinator

[ https://issues.apache.org/jira/browse/KAFKA-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yishun Guan updated KAFKA-7206: --- Description: To quote [~guozhang] : "The proposal is that, we extend FindCoordinatorRequest to have

[jira] [Updated] (KAFKA-7206) Enable batching in FindCoordinator

[ https://issues.apache.org/jira/browse/KAFKA-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yishun Guan updated KAFKA-7206: --- Labels: newbie++ (was: ) > Enable batching in FindCoordinator > --

[jira] [Created] (KAFKA-7206) Enable batching in FindCoordinator

Yishun Guan created KAFKA-7206: -- Summary: Enable batching in FindCoordinator Key: KAFKA-7206 URL: https://issues.apache.org/jira/browse/KAFKA-7206 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556289#comment-16556289 ] Dong Lin commented on KAFKA-7190: - Thanks you [~mjsax] [~guozhang] for the discussion. > Under low

[jira] [Commented] (KAFKA-7128) Lagging high watermark can lead to committed data loss after ISR expansion

[ https://issues.apache.org/jira/browse/KAFKA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556277#comment-16556277 ] Dong Lin commented on KAFKA-7128: - BTW, if we want to make sure there is no message loss, it may be

[jira] [Commented] (KAFKA-7128) Lagging high watermark can lead to committed data loss after ISR expansion

[ https://issues.apache.org/jira/browse/KAFKA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556274#comment-16556274 ] Dong Lin commented on KAFKA-7128: - Thanks for the explanation [~hachikuji]. I slightly modified the

[jira] [Updated] (KAFKA-7128) Lagging high watermark can lead to committed data loss after ISR expansion

[ https://issues.apache.org/jira/browse/KAFKA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7128: Description: Some model checking exposed a weakness in the ISR expansion logic. We know that the high

[jira] [Created] (KAFKA-7205) KafkaConsumer / KafkaProducer should allow Reconfiguration of SSL Configuration

Magnus Jungsbluth created KAFKA-7205: Summary: KafkaConsumer / KafkaProducer should allow Reconfiguration of SSL Configuration Key: KAFKA-7205 URL: https://issues.apache.org/jira/browse/KAFKA-7205

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556238#comment-16556238 ] Guozhang Wang commented on KAFKA-7190: -- [~lindong] That's a good point. I think maybe we would not

[jira] [Created] (KAFKA-7204) MockConsumer poll clears all records in poll(), including records for subscriptions that are paused.

Subodh Bhattacharjya created KAFKA-7204: --- Summary: MockConsumer poll clears all records in poll(), including records for subscriptions that are paused. Key: KAFKA-7204 URL:

[jira] [Commented] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556120#comment-16556120 ] ASF GitHub Bot commented on KAFKA-3522: --- mjsax opened a new pull request #5422: [WIP: DO NOT MERGE]

[jira] [Commented] (KAFKA-7131) Update release script to generate announcement email text

[ https://issues.apache.org/jira/browse/KAFKA-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556074#comment-16556074 ] Matthias J. Sax commented on KAFKA-7131: Thanks [~bibin84]! I added you to the list of

[jira] [Assigned] (KAFKA-7131) Update release script to generate announcement email text

[ https://issues.apache.org/jira/browse/KAFKA-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-7131: -- Assignee: bibin sebastian > Update release script to generate announcement email text

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556070#comment-16556070 ] Matthias J. Sax commented on KAFKA-7190: Good point. You are right, consumers in

[jira] [Comment Edited] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556053#comment-16556053 ] Dong Lin edited comment on KAFKA-7190 at 7/25/18 5:53 PM: -- [~mjsax] I guess one

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556053#comment-16556053 ] Dong Lin commented on KAFKA-7190: -     [~mjsax] I guess one question is, if LSO is defined for a

[jira] [Comment Edited] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556053#comment-16556053 ] Dong Lin edited comment on KAFKA-7190 at 7/25/18 5:52 PM: -- [~mjsax] I guess one

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556042#comment-16556042 ] Matthias J. Sax commented on KAFKA-7190: > The main reason we need to prevent client from

[jira] [Commented] (KAFKA-7203) Improve Streams StickyTaskAssingor

[ https://issues.apache.org/jira/browse/KAFKA-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556041#comment-16556041 ] Guozhang Wang commented on KAFKA-7203: -- Yeah, good point. > Improve Streams StickyTaskAssingor >

[jira] [Commented] (KAFKA-7192) State-store can desynchronise with changelog

[ https://issues.apache.org/jira/browse/KAFKA-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556021#comment-16556021 ] Matthias J. Sax commented on KAFKA-7192: It's expected that the checkpoint file is one lower,

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556011#comment-16556011 ] Dong Lin commented on KAFKA-7190: - [~guozhang] Certainly, I am happy to make the modification after we

[jira] [Commented] (KAFKA-7203) Improve Streams StickyTaskAssingor

[ https://issues.apache.org/jira/browse/KAFKA-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555999#comment-16555999 ] Matthias J. Sax commented on KAFKA-7203: Maybe KAFKA-4969 even completely contains this ticket.

[jira] [Resolved] (KAFKA-5799) New KafkaSpoutConfig(Scheme)-ByteArrayKeyValueScheme

[ https://issues.apache.org/jira/browse/KAFKA-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5799. -- Resolution: Auto Closed Closing Apache Storm - Kafka Spout related query.  If this still issue, please

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555990#comment-16555990 ] Guozhang Wang commented on KAFKA-7190: -- I've discussed about this with [~hachikuji] and here are our

[jira] [Commented] (KAFKA-5962) java.io.IOException: Map failed

[ https://issues.apache.org/jira/browse/KAFKA-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555738#comment-16555738 ] Manikumar commented on KAFKA-5962: -- some info here: https://issues.apache.org/jira/browse/KAFKA-6343 >

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555730#comment-16555730 ] lambdaliu commented on KAFKA-7190: -- Hello [~mjsax]  [~guozhang], sorry for the late reply. I also agree

[jira] [Commented] (KAFKA-6690) Priorities for Source Topics

[ https://issues.apache.org/jira/browse/KAFKA-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555919#comment-16555919 ] Guozhang Wang commented on KAFKA-6690: -- [~balaprassanna] Your description on the JIRA seems to be

[jira] [Comment Edited] (KAFKA-2395) Linked to a interfaces even though the host.name had config

[ https://issues.apache.org/jira/browse/KAFKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1610#comment-1610 ] Manikumar edited comment on KAFKA-2395 at 7/25/18 10:42 AM: extra port is

[jira] [Resolved] (KAFKA-2395) Linked to a interfaces even though the host.name had config

[ https://issues.apache.org/jira/browse/KAFKA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2395. -- Resolution: Not A Problem extra port is related to KAFKA-1869 > Linked to a interfaces even though

[jira] [Commented] (KAFKA-7192) State-store can desynchronise with changelog

[ https://issues.apache.org/jira/browse/KAFKA-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555650#comment-16555650 ] Jon Bates commented on KAFKA-7192: -- Great; thanks! We came up with a similar general solution (delete

[jira] [Comment Edited] (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=16555485#comment-16555485 ] Don edited comment on KAFKA-3042 at 7/25/18 10:21 AM: -- We tried reproducing the

[jira] [Resolved] (KAFKA-2396) I have config host.name and advertised.host.name but still have a link connet to 0.0.0.0 with random port

[ https://issues.apache.org/jira/browse/KAFKA-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2396. -- Resolution: Not A Problem extra port is related to JMX. See  KAFKA-1869 > I have config host.name and

[jira] [Comment Edited] (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=16555485#comment-16555485 ] Don edited comment on KAFKA-3042 at 7/25/18 10:21 AM: -- We tried reproducing the

[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=16555485#comment-16555485 ] Don commented on KAFKA-3042: We tried reproducing the issue on confluent docker image 4.1.0 by commenting

[jira] [Commented] (KAFKA-6690) Priorities for Source Topics

[ https://issues.apache.org/jira/browse/KAFKA-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555472#comment-16555472 ] Bala Prassanna I commented on KAFKA-6690: - Would be helpful if the same option is also present in

[jira] [Resolved] (KAFKA-7159) mark configuration files in confluent-kafka RPM SPEC file

[ https://issues.apache.org/jira/browse/KAFKA-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Sasvari resolved KAFKA-7159. --- Resolution: Won't Fix > mark configuration files in confluent-kafka RPM SPEC file >