[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838918#comment-15838918 ] Jeff Widman commented on KAFKA-3806: Too often people not super familiar with Kafka don't realize the

[jira] [Commented] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832378#comment-15832378 ] Jeff Widman commented on KAFKA-2000: If neither of them is interested, I'm happy to cleanup the

[jira] [Comment Edited] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832378#comment-15832378 ] Jeff Widman edited comment on KAFKA-2000 at 1/20/17 8:45 PM: - If neither of

[jira] [Commented] (KAFKA-4682) Committed offsets should not be deleted if a consumer is still active

[ https://issues.apache.org/jira/browse/KAFKA-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832697#comment-15832697 ] Jeff Widman commented on KAFKA-4682: Now that consumers have background heartbeat thread, it should be

[jira] [Comment Edited] (KAFKA-4682) Committed offsets should not be deleted if a consumer is still active

[ https://issues.apache.org/jira/browse/KAFKA-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832697#comment-15832697 ] Jeff Widman edited comment on KAFKA-4682 at 1/21/17 1:08 AM: - Now that

[jira] [Commented] (KAFKA-4517) Remove kafka-consumer-offset-checker.sh script since already deprecated in Kafka 9

[ https://issues.apache.org/jira/browse/KAFKA-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836818#comment-15836818 ] Jeff Widman commented on KAFKA-4517: So what are the next actions here since I've got an outstanding

[jira] [Commented] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

[ https://issues.apache.org/jira/browse/KAFKA-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827769#comment-15827769 ] Jeff Widman commented on KAFKA-4668: Also KAFKA-3848 > Mirrormaker should default to

[jira] [Created] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

Jeff Widman created KAFKA-4668: -- Summary: Mirrormaker should default to auto.offset.reset=earliest Key: KAFKA-4668 URL: https://issues.apache.org/jira/browse/KAFKA-4668 Project: Kafka Issue

[jira] [Commented] (KAFKA-2410) Implement "Auto Topic Creation" client side and remove support from Broker side

[ https://issues.apache.org/jira/browse/KAFKA-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824382#comment-15824382 ] Jeff Widman commented on KAFKA-2410: I strongly support removing it from the Broker. But does it need

[jira] [Commented] (KAFKA-3853) Report offsets for empty groups in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828620#comment-15828620 ] Jeff Widman commented on KAFKA-3853: Thanks again for this! Really looking forward to it. > Report

[jira] [Commented] (KAFKA-4095) When a topic is deleted and then created with the same name, 'committed' offsets are not reset

[ https://issues.apache.org/jira/browse/KAFKA-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889093#comment-15889093 ] Jeff Widman commented on KAFKA-4095: Wasn't this solved by KAFKA-2000? At least for the new consumers

[jira] [Commented] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657823#comment-15657823 ] Jeff Widman commented on KAFKA-2076: It'd be great to see this move forward. > Add an API to new

[jira] [Commented] (KAFKA-1941) Timeout connections in the clients

[ https://issues.apache.org/jira/browse/KAFKA-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15674679#comment-15674679 ] Jeff Widman commented on KAFKA-1941: Shouldn't this be closed? I think it was handled in KAFKA-1282,

[jira] [Comment Edited] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658812#comment-15658812 ] Jeff Widman edited comment on KAFKA-2076 at 11/12/16 2:22 AM: -- Thanks

[jira] [Comment Edited] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658812#comment-15658812 ] Jeff Widman edited comment on KAFKA-2076 at 11/12/16 2:21 AM: -- Thanks

[jira] [Commented] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658812#comment-15658812 ] Jeff Widman commented on KAFKA-2076: Thanks [~becket_qin], BTW great presentation at the Kafka meetup

[jira] [Commented] (KAFKA-4254) Questionable handling of unknown partitions in KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575850#comment-15575850 ] Jeff Widman commented on KAFKA-4254: Does this affect 10.0 or just 10.1? > Questionable handling of

[jira] [Commented] (KAFKA-3853) Report offsets for empty groups in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736740#comment-15736740 ] Jeff Widman commented on KAFKA-3853: Any idea if this will land in 0.10.2? > Report offsets for empty

[jira] [Commented] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750082#comment-15750082 ] Jeff Widman commented on KAFKA-3135: Can the tags on this issue be updated to note that it applies to

[jira] [Created] (KAFKA-4519) Delete old unused branches in git repo

Jeff Widman created KAFKA-4519: -- Summary: Delete old unused branches in git repo Key: KAFKA-4519 URL: https://issues.apache.org/jira/browse/KAFKA-4519 Project: Kafka Issue Type: Task

[jira] [Created] (KAFKA-4517) Remove shell scripts deprecated in Kafka 9

Jeff Widman created KAFKA-4517: -- Summary: Remove shell scripts deprecated in Kafka 9 Key: KAFKA-4517 URL: https://issues.apache.org/jira/browse/KAFKA-4517 Project: Kafka Issue Type: Task

[jira] [Updated] (KAFKA-4517) Remove kafka-consumer-offset-checker.sh script since already deprecated in Kafka 9

[ https://issues.apache.org/jira/browse/KAFKA-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-4517: --- Summary: Remove kafka-consumer-offset-checker.sh script since already deprecated in Kafka 9 (was:

[jira] [Updated] (KAFKA-4517) Remove kafka-consumer-offset-checker.sh script since deprecated in Kafka 9

[ https://issues.apache.org/jira/browse/KAFKA-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-4517: --- Summary: Remove kafka-consumer-offset-checker.sh script since deprecated in Kafka 9 (was: Remove

[jira] [Created] (KAFKA-4621) Fetch Request V3 docs list max_bytes twice

Jeff Widman created KAFKA-4621: -- Summary: Fetch Request V3 docs list max_bytes twice Key: KAFKA-4621 URL: https://issues.apache.org/jira/browse/KAFKA-4621 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-4621) Fetch Request V3 docs list max_bytes twice

[ https://issues.apache.org/jira/browse/KAFKA-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819844#comment-15819844 ] Jeff Widman commented on KAFKA-4621: Yeah, I saw that... perhaps the descriptions could also be

[jira] [Commented] (KAFKA-1817) AdminUtils.createTopic vs kafka-topics.sh --create with partitions

[ https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803174#comment-15803174 ] Jeff Widman commented on KAFKA-1817: So can this be closed? > AdminUtils.createTopic vs

[jira] [Commented] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15788686#comment-15788686 ] Jeff Widman commented on KAFKA-3135: It's not currently a critical issue for my company. Typically

[jira] [Commented] (KAFKA-3297) More optimally balanced partition assignment strategy (new consumer)

[ https://issues.apache.org/jira/browse/KAFKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15786986#comment-15786986 ] Jeff Widman commented on KAFKA-3297: [~ewencp] KIP-54 tackles both sticky re-assignments and a more

[jira] [Commented] (KAFKA-242) Subsequent calls of ConsumerConnector.createMessageStreams cause Consumer offset to be incorrect

[ https://issues.apache.org/jira/browse/KAFKA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765835#comment-15765835 ] Jeff Widman commented on KAFKA-242: --- Does this bug still exist in 0.10? > Subsequent calls of

[jira] [Commented] (KAFKA-2196) remove roundrobin identical topic constraint in consumer coordinator

[ https://issues.apache.org/jira/browse/KAFKA-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766440#comment-15766440 ] Jeff Widman commented on KAFKA-2196: What version did this land in? > remove roundrobin identical

[jira] [Commented] (KAFKA-2019) RoundRobinAssignor clusters by consumer

[ https://issues.apache.org/jira/browse/KAFKA-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766498#comment-15766498 ] Jeff Widman commented on KAFKA-2019: As noted in KIP-54

[jira] [Commented] (KAFKA-2172) Round-robin partition assignment strategy too restrictive

[ https://issues.apache.org/jira/browse/KAFKA-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766445#comment-15766445 ] Jeff Widman commented on KAFKA-2172: Should this be marked as resolved? KAFKA-2196 added this to the

[jira] [Commented] (KAFKA-3297) More optimally balanced partition assignment strategy (new consumer)

[ https://issues.apache.org/jira/browse/KAFKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766465#comment-15766465 ] Jeff Widman commented on KAFKA-3297: Was this KIP ever voted on? I see there's only a handful of

[jira] [Comment Edited] (KAFKA-3297) More optimally balanced partition assignment strategy (new consumer)

[ https://issues.apache.org/jira/browse/KAFKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766465#comment-15766465 ] Jeff Widman edited comment on KAFKA-3297 at 12/21/16 8:38 AM: -- Is this being

[jira] [Commented] (KAFKA-2331) Kafka does not spread partitions in a topic among all consumers evenly

[ https://issues.apache.org/jira/browse/KAFKA-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766509#comment-15766509 ] Jeff Widman commented on KAFKA-2331: Isn't this what round robin partitioning strategy was trying to

[jira] [Commented] (KAFKA-3853) Report offsets for empty groups in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15759588#comment-15759588 ] Jeff Widman commented on KAFKA-3853: Did the KIP get the missing vote required to pass? > Report

[jira] [Commented] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15768710#comment-15768710 ] Jeff Widman commented on KAFKA-2273: What was the outcome of the vote? > Add rebalance with a minimal

[jira] [Commented] (KAFKA-4858) Long topic names created using old kafka-topics.sh can prevent newer brokers from joining any ISRs

[ https://issues.apache.org/jira/browse/KAFKA-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929421#comment-15929421 ] Jeff Widman commented on KAFKA-4858: I'd say if you patch it so that replication doesn't break, that's

[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=15959479#comment-15959479 ] Jeff Widman edited comment on KAFKA-3042 at 4/6/17 6:16 PM: We hit this on

[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=15959479#comment-15959479 ] Jeff Widman commented on KAFKA-3042: We hit this on 0.10.0.1. Root cause was a really long zookeeper

[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=15975603#comment-15975603 ] Jeff Widman commented on KAFKA-3042: [~lindong] thanks for the offer to help and sorry for the slow

[jira] [Commented] (KAFKA-4858) Long topic names created using old kafka-topics.sh can prevent newer brokers from joining any ISRs

[ https://issues.apache.org/jira/browse/KAFKA-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903928#comment-15903928 ] Jeff Widman commented on KAFKA-4858: My understanding was that the general expectation was that you

[jira] [Updated] (KAFKA-4790) Kafka cannot recover after a disk full

[ https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-4790: --- Fix Version/s: (was: 0.10.2.1) > Kafka cannot recover after a disk full >

[jira] [Commented] (KAFKA-4858) Long topic names created using old kafka-topics.sh can prevent newer brokers from joining any ISRs

[ https://issues.apache.org/jira/browse/KAFKA-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905917#comment-15905917 ] Jeff Widman commented on KAFKA-4858: I saw the PR ignores those topics... is this a silent failure?

[jira] [Updated] (KAFKA-2273) KIP-54: Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-2273: --- Fix Version/s: 0.11.0.0 > KIP-54: Add rebalance with a minimal number of reassignments to >

[jira] [Commented] (KAFKA-2273) KIP-54: Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898678#comment-15898678 ] Jeff Widman commented on KAFKA-2273: This KIP was accepted, so I added it to the 0.11 milestone >

[jira] [Commented] (KAFKA-4677) Avoid unnecessary task movement across threads during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890935#comment-15890935 ] Jeff Widman commented on KAFKA-4677: Is KIP-54 related since it also implements a sticky partition

[jira] [Resolved] (KAFKA-5299) MirrorMaker with New.consumer doesn't consume message from multiple topics whitelisted

[ https://issues.apache.org/jira/browse/KAFKA-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman resolved KAFKA-5299. Resolution: Cannot Reproduce > MirrorMaker with New.consumer doesn't consume message from multiple

[jira] [Commented] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010801#comment-16010801 ] Jeff Widman commented on KAFKA-3356: Personally, I don't think we need feature parity for the

[jira] [Commented] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030804#comment-16030804 ] Jeff Widman commented on KAFKA-3356: Is there anyway to get this to land today? This is literally

[jira] [Updated] (KAFKA-5381) ERROR Uncaught exception in scheduled task 'delete-expired-consumer-offsets' (kafka.utils.KafkaScheduler)

[ https://issues.apache.org/jira/browse/KAFKA-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-5381: --- Description: We have a 6 node cluster of 0.10.0.1 brokers. Broker 4 had a hardware problem, so we

[jira] [Commented] (KAFKA-4362) Consumer can fail after reassignment of the offsets topic partition

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024997#comment-16024997 ] Jeff Widman commented on KAFKA-4362: Updated the applicable version as we just encountered this on a

[jira] [Updated] (KAFKA-4362) Consumer can fail after reassignment of the offsets topic partition

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-4362: --- Affects Version/s: 0.10.0.1 > Consumer can fail after reassignment of the offsets topic partition >

[jira] [Updated] (KAFKA-5381) ERROR Uncaught exception in scheduled task 'delete-expired-consumer-offsets' (kafka.utils.KafkaScheduler)

[ https://issues.apache.org/jira/browse/KAFKA-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-5381: --- Description: We have a 6 node cluster of 0.10.0.1 brokers. Broker 4 had a hardware problem, so we

[jira] [Updated] (KAFKA-5381) ERROR Uncaught exception in scheduled task 'delete-expired-consumer-offsets' (kafka.utils.KafkaScheduler)

[ https://issues.apache.org/jira/browse/KAFKA-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-5381: --- Description: We have a 6 node cluster of 0.10.0.1 brokers. Broker 4 had a hardware problem, so we