[jira] [Commented] (KAFKA-5694) Add ChangeReplicaDirRequest and DescribeReplicaDirRequest (KIP-113)

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

[jira] [Resolved] (KAFKA-5665) Incorrect interruption invoking method used for Heartbeat thread

[ https://issues.apache.org/jira/browse/KAFKA-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx resolved KAFKA-5665. --- Resolution: Not A Bug > Incorrect interruption invoking method used for Heartbeat thread >

[jira] [Commented] (KAFKA-5665) Incorrect interruption invoking method used for Heartbeat thread

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

[jira] [Commented] (KAFKA-5700) producer missed header information when splitting batches

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

[jira] [Commented] (KAFKA-5678) When the broker graceful shutdown occurs, the producer side sends timeout.

[ https://issues.apache.org/jira/browse/KAFKA-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113845#comment-16113845 ] cuiyang commented on KAFKA-5678: [~becket_qin] I have totally gotten your point, thanks again :) > When

[jira] [Commented] (KAFKA-5358) Consumer perf tool should count rebalance time separately

[ https://issues.apache.org/jira/browse/KAFKA-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113750#comment-16113750 ] Jason Gustafson commented on KAFKA-5358: [~huxi_2b] It seems like the discussion thread on the dev

[jira] [Assigned] (KAFKA-5698) Sort processor node based on name suffix in TopologyDescription.toString()

[ https://issues.apache.org/jira/browse/KAFKA-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5698: Assignee: Guozhang Wang > Sort processor node based on name suffix in

[jira] [Commented] (KAFKA-5698) Sort processor node based on name suffix in TopologyDescription.toString()

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

[jira] [Commented] (KAFKA-5467) setting offset retention minutes to a lower value is not reflecting

[ https://issues.apache.org/jira/browse/KAFKA-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113745#comment-16113745 ] Jason Gustafson commented on KAFKA-5467: [~divyapaulraj92] Can you clarify the steps that you took

[jira] [Commented] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113733#comment-16113733 ] Jason Gustafson commented on KAFKA-5407: [~fvegaucr] Can you attach the broker logs from that time

[jira] [Created] (KAFKA-5699) Validate and Create connector endpoint should take the same format message body

Robin Moffatt created KAFKA-5699: Summary: Validate and Create connector endpoint should take the same format message body Key: KAFKA-5699 URL: https://issues.apache.org/jira/browse/KAFKA-5699

[jira] [Commented] (KAFKA-2507) Replace ControlledShutdown{Request,Response} with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113677#comment-16113677 ] Ismael Juma commented on KAFKA-2507: [~hachikuji] adapted the Java request classes so that they

[jira] [Resolved] (KAFKA-2507) Replace ControlledShutdown{Request,Response} with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2507. Resolution: Fixed Assignee: Jason Gustafson (was: Grant Henke) Fix Version/s:

[jira] [Resolved] (KAFKA-2959) Remove temporary mapping to deserialize functions in RequestChannel

[ https://issues.apache.org/jira/browse/KAFKA-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2959. Resolution: Fixed Assignee: Jason Gustafson Fix Version/s: 1.0.0 > Remove temporary

[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=16113645#comment-16113645 ] Onur Karaman commented on KAFKA-1120: - Alright I might know what's happening. Here's the red flag:

[jira] [Created] (KAFKA-5698) Sort processor node based on name suffix in TopologyDescription.toString()

Guozhang Wang created KAFKA-5698: Summary: Sort processor node based on name suffix in TopologyDescription.toString() Key: KAFKA-5698 URL: https://issues.apache.org/jira/browse/KAFKA-5698 Project:

[jira] [Created] (KAFKA-5697) StreamThread.close() need to interrupt the stream threads to break the loop

Guozhang Wang created KAFKA-5697: Summary: StreamThread.close() need to interrupt the stream threads to break the loop Key: KAFKA-5697 URL: https://issues.apache.org/jira/browse/KAFKA-5697 Project:

[jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113590#comment-16113590 ] Sumant Tambe commented on KAFKA-5621: - Thread closed. Please share your thoughts on KIP-91 [DISCUSS]

[jira] [Comment Edited] (KAFKA-5684) KStreamPrintProcessor as customized KStreamPeekProcessor

[ https://issues.apache.org/jira/browse/KAFKA-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113499#comment-16113499 ] Guozhang Wang edited comment on KAFKA-5684 at 8/3/17 9:10 PM: -- I have a

[jira] [Commented] (KAFKA-5684) KStreamPrintProcessor as customized KStreamPeekProcessor

[ https://issues.apache.org/jira/browse/KAFKA-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113499#comment-16113499 ] Guozhang Wang commented on KAFKA-5684: -- I have a slightly different idea: 1. Remove the

[jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113406#comment-16113406 ] Ismael Juma commented on KAFKA-5621: Yes, let's start the KIP discussion in the mailing list so that

[jira] [Created] (KAFKA-5696) SourceConnector does not commit offset on reconfiguration

Oleg Kuznetsov created KAFKA-5696: - Summary: SourceConnector does not commit offset on reconfiguration Key: KAFKA-5696 URL: https://issues.apache.org/jira/browse/KAFKA-5696 Project: Kafka

[jira] [Comment Edited] (KAFKA-5638) Inconsistency in consumer group related ACLs

[ https://issues.apache.org/jira/browse/KAFKA-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1611#comment-1611 ] Vahid Hashemian edited comment on KAFKA-5638 at 8/3/17 7:50 PM: The

[jira] [Commented] (KAFKA-5638) Inconsistency in consumer group related ACLs

[ https://issues.apache.org/jira/browse/KAFKA-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1611#comment-1611 ] Vahid Hashemian commented on KAFKA-5638: The current usage is probably not incorrect, because the

[jira] [Commented] (KAFKA-5678) When the broker graceful shutdown occurs, the producer side sends timeout.

[ https://issues.apache.org/jira/browse/KAFKA-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113064#comment-16113064 ] Jiangjie Qin commented on KAFKA-5678: - [~cuiyang] 1. Currently request timeout is used in two

[jira] [Commented] (KAFKA-5638) Inconsistency in consumer group related ACLs

[ https://issues.apache.org/jira/browse/KAFKA-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113013#comment-16113013 ] Jason Gustafson commented on KAFKA-5638: Yes, compatibility is what I had in mind. I think my

[jira] [Assigned] (KAFKA-4541) Add capability to create delegation token

[ https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-4541: Assignee: Manikumar (was: Ashish Singh) > Add capability to create delegation token >

[jira] [Commented] (KAFKA-4541) Add capability to create delegation token

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

[jira] [Updated] (KAFKA-5692) Refactor PreferredReplicaLeaderElectionCommand to use AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Bentley updated KAFKA-5692: --- Issue Type: Improvement (was: Bug) > Refactor PreferredReplicaLeaderElectionCommand to use

[jira] [Commented] (KAFKA-3268) Refactor existing CLI scripts to use KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112603#comment-16112603 ] Tom Bentley commented on KAFKA-3268: [~viktorsomogyi] there is no tracking JIRA that I'm aware of.

[jira] [Commented] (KAFKA-3268) Refactor existing CLI scripts to use KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112591#comment-16112591 ] Viktor Somogyi commented on KAFKA-3268: --- [~tombentley], thanks for the heads up, I didn't know about

[jira] [Updated] (KAFKA-3268) Refactor existing CLI scripts to use KafkaAdminClient

[ https://issues.apache.org/jira/browse/KAFKA-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi updated KAFKA-3268: -- Summary: Refactor existing CLI scripts to use KafkaAdminClient (was: Refactor existing CLI

[jira] [Commented] (KAFKA-5561) Rewrite TopicCommand using the new Admin client

[ https://issues.apache.org/jira/browse/KAFKA-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112457#comment-16112457 ] Mickael Maison commented on KAFKA-5561: --- We have pretty restrictive create topic policies to ensure

[jira] [Commented] (KAFKA-5674) max.connections.per.ip minimum value to be zero to allow IP address blocking

[ https://issues.apache.org/jira/browse/KAFKA-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112426#comment-16112426 ] Viktor Somogyi commented on KAFKA-5674: --- [~tmgstev] could you please review my PR once you have

[jira] [Commented] (KAFKA-5693) TopicCreationPolicy and AlterConfigsPolicy overlap

[ https://issues.apache.org/jira/browse/KAFKA-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112403#comment-16112403 ] Tom Bentley commented on KAFKA-5693: Would this need a KIP? It's not changing a public API, as such,

[jira] [Updated] (KAFKA-5692) Refactor PreferredReplicaLeaderElectionCommand to use AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Bentley updated KAFKA-5692: --- Labels: kip (was: needs-kip) > Refactor PreferredReplicaLeaderElectionCommand to use AdminClient >