[jira] [Commented] (KAFKA-6791) Add a CoordinatorNodeProvider in KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197411#comment-17197411 ] Jeff Widman commented on KAFKA-6791: Should this be closed as "wontfix"? The associ

[jira] [Comment Edited] (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&focusedCommentId=17081137#comment-17081137 ] Jeff Widman edited comment on KAFKA-4668 at 4/11/20, 4:44 AM: -

[jira] [Comment Edited] (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&focusedCommentId=17081137#comment-17081137 ] Jeff Widman edited comment on KAFKA-4668 at 4/11/20, 4:44 AM: -

[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&focusedCommentId=17081137#comment-17081137 ] Jeff Widman commented on KAFKA-4668: Going to try to get this across the line, three

[jira] [Assigned] (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:all-tabpanel ] Jeff Widman reassigned KAFKA-4668: -- Assignee: Jeff Widman > Mirrormaker should default to auto.offset.reset=earliest > ---

[jira] [Updated] (KAFKA-7278) replaceSegments() should not call asyncDeleteSegment() for segments which have been removed from segments list

[ https://issues.apache.org/jira/browse/KAFKA-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-7278: --- Description: Currently Log.replaceSegments() will call `asyncDeleteSegment(...)` for every segment l

[jira] [Updated] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is invalid

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-6266: --- Affects Version/s: 1.0.1 > Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of

[jira] [Comment Edited] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440212#comment-16440212 ] Jeff Widman edited comment on KAFKA-6266 at 4/17/18 1:07 AM: -

[jira] [Commented] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is inval

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440212#comment-16440212 ] Jeff Widman commented on KAFKA-6266: I am hitting this after upgrading a 0.10.0.1 brok

[jira] [Updated] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is invalid

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-6266: --- Description: I upgraded Kafka from 0.10.2.1 to 1.0.0 version. From then, I see the below warnings in

[jira] [Updated] (KAFKA-6529) Broker leaks memory and file descriptors after sudden client disconnects

[ https://issues.apache.org/jira/browse/KAFKA-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-6529: --- Fix Version/s: (was: 1.0.2) 1.0.1 > Broker leaks memory and file descriptors af

[jira] [Commented] (KAFKA-6547) group offset reset and begin_offset ignored/no effect

[ https://issues.apache.org/jira/browse/KAFKA-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357807#comment-16357807 ] Jeff Widman commented on KAFKA-6547: What is the specific command you are running? Ho

[jira] [Comment Edited] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357203#comment-16357203 ] Jeff Widman edited comment on KAFKA-2435 at 2/8/18 4:54 PM: Ca

[jira] [Comment Edited] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357203#comment-16357203 ] Jeff Widman edited comment on KAFKA-2435 at 2/8/18 4:51 PM: Ca

[jira] [Comment Edited] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357203#comment-16357203 ] Jeff Widman edited comment on KAFKA-2435 at 2/8/18 4:51 PM: Ca

[jira] [Commented] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357203#comment-16357203 ] Jeff Widman commented on KAFKA-2435: Can this be closed as wontfix?  Two reasons:  

[jira] [Updated] (KAFKA-6058) KIP-222: Add "describe consumer groups" and "list consumer groups" to KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-6058: --- Labels: kip-222 (was: needs-kip) > KIP-222: Add "describe consumer groups" and "list consumer groups"

[jira] [Updated] (KAFKA-6058) KIP-222: Add "describe consumer groups" and "list consumer groups" to KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-6058: --- Summary: KIP-222: Add "describe consumer groups" and "list consumer groups" to KafkaAdminClient (was:

[jira] [Commented] (KAFKA-6058) KIP-222: Add "describe consumer groups" and "list consumer groups" to KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336639#comment-16336639 ] Jeff Widman commented on KAFKA-6058: Note that listing group offsets has also been add

[jira] [Updated] (KAFKA-6058) Add "describe consumer groups" and "list consumer groups" to KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-6058: --- Description: {{KafkaAdminClient}} does not allow to get information about consumer groups. This featu

[jira] [Commented] (KAFKA-6469) ISR change notification queue can prevent controller from making progress

[ https://issues.apache.org/jira/browse/KAFKA-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336114#comment-16336114 ] Jeff Widman commented on KAFKA-6469: We hit a similar issue when doing partition re-as

[jira] [Updated] (KAFKA-6185) Selector memory leak with high likelihood of OOM in case of down conversion

[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-6185: --- Component/s: core > Selector memory leak with high likelihood of OOM in case of down conversion >

[jira] [Updated] (KAFKA-5083) always leave the last surviving member of the ISR in ZK

[ https://issues.apache.org/jira/browse/KAFKA-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-5083: --- Fix Version/s: 1.1.0 > always leave the last surviving member of the ISR in ZK > -

[jira] [Comment Edited] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331093#comment-16331093 ] Jeff Widman edited comment on KAFKA-1120 at 1/18/18 7:58 PM: -

[jira] [Commented] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331093#comment-16331093 ] Jeff Widman commented on KAFKA-1120: The issue description says "the broker will be in

[jira] [Comment Edited] (KAFKA-2758) Improve Offset Commit Behavior

[ https://issues.apache.org/jira/browse/KAFKA-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240796#comment-16240796 ] Jeff Widman edited comment on KAFKA-2758 at 11/6/17 7:59 PM: -

[jira] [Comment Edited] (KAFKA-2758) Improve Offset Commit Behavior

[ https://issues.apache.org/jira/browse/KAFKA-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240796#comment-16240796 ] Jeff Widman edited comment on KAFKA-2758 at 11/6/17 7:59 PM: -

[jira] [Comment Edited] (KAFKA-2758) Improve Offset Commit Behavior

[ https://issues.apache.org/jira/browse/KAFKA-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240796#comment-16240796 ] Jeff Widman edited comment on KAFKA-2758 at 11/6/17 7:59 PM: -

[jira] [Commented] (KAFKA-2758) Improve Offset Commit Behavior

[ https://issues.apache.org/jira/browse/KAFKA-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240796#comment-16240796 ] Jeff Widman commented on KAFKA-2758: item 1 would be significantly more useful if [KI

[jira] [Commented] (KAFKA-4950) ConcurrentModificationException when iterating over Kafka Metrics

[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240766#comment-16240766 ] Jeff Widman commented on KAFKA-4950: Should the component here be (new) consumer? Or d

[jira] [Commented] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225870#comment-16225870 ] Jeff Widman commented on KAFKA-4084: [~junrao] any ballpark quantification to "much fa

[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&focusedCommentId=16148417#comment-16148417 ] Jeff Widman commented on KAFKA-3356: Is this waiting on anything to be merged? > Remo

[jira] [Updated] (KAFKA-5584) Incorrect log size for topics larger than 2 GB

[ https://issues.apache.org/jira/browse/KAFKA-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-5584: --- Description: The {{size}} of a {{Log}} is calculated incorrectly due to an Integer overflow. For larg

[jira] [Commented] (KAFKA-5584) Incorrect log size for topics larger than 2 GB

[ https://issues.apache.org/jira/browse/KAFKA-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083580#comment-16083580 ] Jeff Widman commented on KAFKA-5584: What version of Kafka did you observe this on? >

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16069438#comment-16069438 ] Jeff Widman commented on KAFKA-5299: The first (non-working) is not a valid regex, or

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16069006#comment-16069006 ] Jeff Widman commented on KAFKA-5299: Closing due to lack of activity and inadequate de

[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 t

[jira] [Commented] (KAFKA-5027) Kafka Controller Redesign

[ https://issues.apache.org/jira/browse/KAFKA-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061806#comment-16061806 ] Jeff Widman commented on KAFKA-5027: Just wanted to say thanks [~onurkaraman] for all

[jira] [Commented] (KAFKA-5465) FetchResponse v0 does not return any messages when max_bytes smaller than v2 message set

[ https://issues.apache.org/jira/browse/KAFKA-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054956#comment-16054956 ] Jeff Widman commented on KAFKA-5465: I agree with the "WontFix" resolution; however, I

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054955#comment-16054955 ] Jeff Widman commented on KAFKA-5473: Saw this was tagged as 0.9.0... Does this affect