[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293473#comment-16293473 ] Jun Rao commented on KAFKA-3410: [~wushujames], yes, KAFKA-1211 should help address this. Do you want to

[jira] [Assigned] (KAFKA-6265) GlobalKTable missing #queryableStoreName()

[ https://issues.apache.org/jira/browse/KAFKA-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-6265: -- Assignee: Richard Yu > GlobalKTable missing #queryableStoreName() >

[jira] [Assigned] (KAFKA-4999) Add convenience overload for seek* methods

[ https://issues.apache.org/jira/browse/KAFKA-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4999: -- Assignee: Richard Yu > Add convenience overload for seek* methods >

[jira] [Commented] (KAFKA-6265) GlobalKTable missing #queryableStoreName()

[ https://issues.apache.org/jira/browse/KAFKA-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293467#comment-16293467 ] Matthias J. Sax commented on KAFKA-6265: [~Yohan123] Please assign ticket to yourself when you

[jira] [Updated] (KAFKA-6375) Follower replicas can never catch up to be ISR due to creating ReplicaFetcherThread failed.

[ https://issues.apache.org/jira/browse/KAFKA-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Tang updated KAFKA-6375: - Description: Hi, I met with a case that in one broker, the out of sync replicas never catch up. When the

[jira] [Commented] (KAFKA-6375) Follower replicas can never catch up to be ISR due to creating ReplicaFetcherThread failed.

[ https://issues.apache.org/jira/browse/KAFKA-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293576#comment-16293576 ] huxihx commented on KAFKA-6375: --- “ Unable to establish loopback connection” Did you disable the firewall? >

[jira] [Commented] (KAFKA-6302) Topic can not be recreated after it is deleted

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

[jira] [Assigned] (KAFKA-6302) Topic can not be recreated after it is deleted

[ https://issues.apache.org/jira/browse/KAFKA-6302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-6302: -- Assignee: Matthias J. Sax > Topic can not be recreated after it is deleted >

[jira] [Commented] (KAFKA-6265) GlobalKTable missing #queryableStoreName()

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

[jira] [Commented] (KAFKA-6370) MirrorMakerIntegrationTest#testCommaSeparatedRegex may fail due to NullPointerException

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

[jira] [Commented] (KAFKA-6086) Provide for custom error handling when Kafka Streams fails to produce

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

[jira] [Commented] (KAFKA-6365) How to add a client to list of available clients?

[ https://issues.apache.org/jira/browse/KAFKA-6365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292559#comment-16292559 ] Lev Gorodinski commented on KAFKA-6365: --- Hi [~hachikuji], just following up on this. I'm logged in,

[jira] [Commented] (KAFKA-6371) FetchMetadata creates unneeded Strings on instantiation

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

[jira] [Commented] (KAFKA-6371) FetchMetadata creates unneeded Strings on instantiation

[ https://issues.apache.org/jira/browse/KAFKA-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292268#comment-16292268 ] huxihx commented on KAFKA-6371: --- Seems it's already fixed in

[jira] [Created] (KAFKA-6371) FetchMetadata creates unneeded Strings on instantiation

Maytee Chinavanichkit created KAFKA-6371: Summary: FetchMetadata creates unneeded Strings on instantiation Key: KAFKA-6371 URL: https://issues.apache.org/jira/browse/KAFKA-6371 Project: Kafka

[jira] [Created] (KAFKA-6374) Constant Consumer Errors after replacing a broker

Aravind Velamur Srinivasan created KAFKA-6374: - Summary: Constant Consumer Errors after replacing a broker Key: KAFKA-6374 URL: https://issues.apache.org/jira/browse/KAFKA-6374 Project:

[jira] [Updated] (KAFKA-6374) Constant Consumer Errors after replacing a broker

[ https://issues.apache.org/jira/browse/KAFKA-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravind Velamur Srinivasan updated KAFKA-6374: -- Description: We had to replace one of the brokers for maintenance

[jira] [Commented] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293291#comment-16293291 ] James Cheng commented on KAFKA-3955: [~ijuma], I said in my comment that: {quote} Note that it is only

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293294#comment-16293294 ] James Cheng commented on KAFKA-3410: Do we think KAFKA-1211 resolves this? If so, should we set Fix

[jira] [Comment Edited] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293291#comment-16293291 ] James Cheng edited comment on KAFKA-3955 at 12/15/17 9:45 PM: -- [~ijuma], I

[jira] [Issue Comment Deleted] (KAFKA-6265) GlobalKTable missing #queryableStoreName()

[ https://issues.apache.org/jira/browse/KAFKA-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-6265: -- Comment: was deleted (was: I am not sure if this is a second way to instantiate it: (I found it in

[jira] [Commented] (KAFKA-6265) GlobalKTable missing #queryableStoreName()

[ https://issues.apache.org/jira/browse/KAFKA-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293320#comment-16293320 ] Richard Yu commented on KAFKA-6265: --- I am not sure if this is a second way to instantiate it: (I found

[jira] [Created] (KAFKA-6375) Follower replicas can never catch up to be ISR due to creating ReplicaFetcherThread failed.

Rong Tang created KAFKA-6375: Summary: Follower replicas can never catch up to be ISR due to creating ReplicaFetcherThread failed. Key: KAFKA-6375 URL: https://issues.apache.org/jira/browse/KAFKA-6375

[jira] [Commented] (KAFKA-6363) Use MockAdminClient for any unit tests that depend on AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292887#comment-16292887 ] Guozhang Wang commented on KAFKA-6363: -- Currently {{MockKafkaAdminClientEnv}} is used in these tests:

[jira] [Commented] (KAFKA-6359) Work for KIP-236

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

[jira] [Commented] (KAFKA-5526) KIP-175: ConsumerGroupCommand no longer shows output for consumer groups which have not committed offsets

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

[jira] [Commented] (KAFKA-6336) when using assign() with kafka consumer the KafkaConsumerGroup command doesnt show those consumers

[ https://issues.apache.org/jira/browse/KAFKA-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293091#comment-16293091 ] Jason Gustafson commented on KAFKA-6336: [~huxi_2b] Good point. Since the protocol type is

[jira] [Created] (KAFKA-6373) Log end offset of input table changing during restore

Charles Crain created KAFKA-6373: Summary: Log end offset of input table changing during restore Key: KAFKA-6373 URL: https://issues.apache.org/jira/browse/KAFKA-6373 Project: Kafka Issue

[jira] [Created] (KAFKA-6372) Trogdor should use LogContext for log messages

Colin P. McCabe created KAFKA-6372: -- Summary: Trogdor should use LogContext for log messages Key: KAFKA-6372 URL: https://issues.apache.org/jira/browse/KAFKA-6372 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-6375) Follower replicas can never catch up to be ISR due to creating ReplicaFetcherThread failed.

[ https://issues.apache.org/jira/browse/KAFKA-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Tang updated KAFKA-6375: - Description: Hi, I met with a case that in one broker, the out of sync replicas never catch up. When the

[jira] [Commented] (KAFKA-6265) GlobalKTable missing #queryableStoreName()

[ https://issues.apache.org/jira/browse/KAFKA-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293344#comment-16293344 ] Guozhang Wang commented on KAFKA-6265: -- That's a good point. {{KStreamBuilder}} is a deprecated

[jira] [Commented] (KAFKA-6336) when using assign() with kafka consumer the KafkaConsumerGroup command doesnt show those consumers

[ https://issues.apache.org/jira/browse/KAFKA-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293343#comment-16293343 ] Neerja Khattar commented on KAFKA-6336: --- [~hachikuji] I did try using --describe and that didn't

[jira] [Updated] (KAFKA-6375) Follower replicas can never catch up to be ISR due to creating ReplicaFetcherThread failed.

[ https://issues.apache.org/jira/browse/KAFKA-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Tang updated KAFKA-6375: - Description: Hi, I met with a case that in one broker, the out of sync replicas never catch up. When the

[jira] [Updated] (KAFKA-6375) Follower replicas can never catch up to be ISR due to creating ReplicaFetcherThread failed.

[ https://issues.apache.org/jira/browse/KAFKA-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Tang updated KAFKA-6375: - Description: Hi, I met with a case that in one broker, the out of sync replicas never catch up. When the

[jira] [Updated] (KAFKA-6375) Follower replicas can never catch up to be ISR due to creating ReplicaFetcherThread failed.

[ https://issues.apache.org/jira/browse/KAFKA-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Tang updated KAFKA-6375: - Description: Hi, I met with a case that in one broker, the out of sync replicas never catch up. When the

[jira] [Updated] (KAFKA-6375) Follower replicas can never catch up to be ISR due to creating ReplicaFetcherThread failed.

[ https://issues.apache.org/jira/browse/KAFKA-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rong Tang updated KAFKA-6375: - Affects Version/s: (was: 0.10.2.0) 0.10.1.0 > Follower replicas can never

[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=16293384#comment-16293384 ] ASF GitHub Bot commented on KAFKA-5473: --- Github user asfgit closed the pull request at: