[jira] [Updated] (KAFKA-5341) Add UnderMinIsrPartitionCount and per-partition UnderMinIsr metrics

[ https://issues.apache.org/jira/browse/KAFKA-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-5341: - Fix Version/s: 1.0.0 > Add UnderMinIsrPartitionCount and per-partition

[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=16102661#comment-16102661 ] ASF GitHub Bot commented on KAFKA-5665: --- GitHub user huxihx opened a pull request:

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102622#comment-16102622 ] huxihx commented on KAFKA-5007: --- [~joseph.alias...@gmail.com] what's the status for this jira? Have you

[jira] [Assigned] (KAFKA-5664) Disable auto offset commit in ConsoleConsumer if no group is provided

[ https://issues.apache.org/jira/browse/KAFKA-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-5664: -- Assignee: Vahid Hashemian > Disable auto offset commit in ConsoleConsumer if no group

[jira] [Commented] (KAFKA-5663) LogDirFailureTest system test fails

[ https://issues.apache.org/jira/browse/KAFKA-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102403#comment-16102403 ] Dong Lin commented on KAFKA-5663: - Thanks [~apurva]. I will look into this. > LogDirFailureTest system

[jira] [Created] (KAFKA-5664) Disable auto offset commit in ConsoleConsumer if no group is provided

Jason Gustafson created KAFKA-5664: -- Summary: Disable auto offset commit in ConsoleConsumer if no group is provided Key: KAFKA-5664 URL: https://issues.apache.org/jira/browse/KAFKA-5664 Project:

[jira] [Created] (KAFKA-5659) AdminClient#describeConfigs makes an extra empty request when only broker info is requested

Colin P. McCabe created KAFKA-5659: -- Summary: AdminClient#describeConfigs makes an extra empty request when only broker info is requested Key: KAFKA-5659 URL: https://issues.apache.org/jira/browse/KAFKA-5659

[jira] [Updated] (KAFKA-5658) Fix AdminClient request timeout handling bug resulting in continual BrokerNotAvailableExceptions

[ https://issues.apache.org/jira/browse/KAFKA-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5658: --- Description: The AdminClient does not properly clear calls from the callsInFlight structure.

[jira] [Updated] (KAFKA-5658) adminclient will stop working after some amount of time

[ https://issues.apache.org/jira/browse/KAFKA-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5658: --- Priority: Critical (was: Major) > adminclient will stop working after some amount of time >

[jira] [Updated] (KAFKA-5658) adminclient will stop working after some amount of time

[ https://issues.apache.org/jira/browse/KAFKA-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5658: --- Fix Version/s: 0.11.0.1 > adminclient will stop working after some amount of time >

[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=16102176#comment-16102176 ] Jiangjie Qin commented on KAFKA-5621: - [~apurva] Yes, I agree that expiry ms is a new concept as it is

[jira] [Updated] (KAFKA-4279) REST endpoint to list converter plugins

[ https://issues.apache.org/jira/browse/KAFKA-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-4279: - Labels: needs-kip newbie (was: ) > REST endpoint to list converter plugins >

[jira] [Created] (KAFKA-5657) Connect REST API should include the connector type when describing a connector

Randall Hauch created KAFKA-5657: Summary: Connect REST API should include the connector type when describing a connector Key: KAFKA-5657 URL: https://issues.apache.org/jira/browse/KAFKA-5657

[jira] [Commented] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102147#comment-16102147 ] Ismael Juma commented on KAFKA-4327: We discussed this at the time and we documented that it's _not_

[jira] [Commented] (KAFKA-5648) make Merger extend Aggregator

[ https://issues.apache.org/jira/browse/KAFKA-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102119#comment-16102119 ] Matthias J. Sax commented on KAFKA-5648: Your observation is correct, that {{Merger}} and

[jira] [Commented] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101966#comment-16101966 ] Ewen Cheslack-Postava commented on KAFKA-4327: -- [~mjsax] We'd have to decide whether the java

[jira] [Commented] (KAFKA-5656) Support bulk attributes request on KafkaMbean where some attributes do not exist

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

[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=16101932#comment-16101932 ] Jiangjie Qin commented on KAFKA-5621: - [~ijuma] [~apurva] The expiration for messages in the

[jira] [Created] (KAFKA-5648) make Merger extend Aggregator

Clemens Valiente created KAFKA-5648: --- Summary: make Merger extend Aggregator Key: KAFKA-5648 URL: https://issues.apache.org/jira/browse/KAFKA-5648 Project: Kafka Issue Type: New Feature

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser

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

[jira] [Commented] (KAFKA-3038) Speeding up partition reassignment after broker failure

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

[jira] [Created] (KAFKA-5646) Use async ZookeeperClient for Config and ISR management

Ismael Juma created KAFKA-5646: -- Summary: Use async ZookeeperClient for Config and ISR management Key: KAFKA-5646 URL: https://issues.apache.org/jira/browse/KAFKA-5646 Project: Kafka Issue

[jira] [Updated] (KAFKA-5642) Use async ZookeeperClient in Controller

[ https://issues.apache.org/jira/browse/KAFKA-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5642: --- Summary: Use async ZookeeperClient in Controller (was: use async ZookeeperClient everywhere) > Use

[jira] [Resolved] (KAFKA-5328) consider switching json parser from scala to jackson

[ https://issues.apache.org/jira/browse/KAFKA-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5328. Resolution: Duplicate Duplicate of KAFKA-1595. > consider switching json parser from scala to

[jira] [Resolved] (KAFKA-3210) Using asynchronous calls through the raw ZK API in ZkUtils

[ https://issues.apache.org/jira/browse/KAFKA-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3210. Resolution: Won't Fix We are following a slightly different approach, see KAFKA-5501. > Using

[jira] [Commented] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101659#comment-16101659 ] Matthias J. Sax commented on KAFKA-4327: It's Streams tool, so it belongs to package

[jira] [Commented] (KAFKA-5386) [Kafka Streams] - custom name for state-store change-log topic

[ https://issues.apache.org/jira/browse/KAFKA-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101652#comment-16101652 ] Matthias J. Sax commented on KAFKA-5386: Understood. Technically, it would be possible to allow

[jira] [Created] (KAFKA-5644) Transient test failure: ResetConsumerGroupOffsetTest.testResetOffsetsToZonedDateTime

Manikumar created KAFKA-5644: Summary: Transient test failure: ResetConsumerGroupOffsetTest.testResetOffsetsToZonedDateTime Key: KAFKA-5644 URL: https://issues.apache.org/jira/browse/KAFKA-5644 Project:

[jira] [Created] (KAFKA-5643) Using _DUCKTAPE_OPTIONS has no effect on executing tests

Paolo Patierno created KAFKA-5643: - Summary: Using _DUCKTAPE_OPTIONS has no effect on executing tests Key: KAFKA-5643 URL: https://issues.apache.org/jira/browse/KAFKA-5643 Project: Kafka

[jira] [Commented] (KAFKA-5562) Do streams state directory cleanup on a single thread

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

[jira] [Comment Edited] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101273#comment-16101273 ] Ismael Juma edited comment on KAFKA-5641 at 7/26/17 7:27 AM: - My comment was

[jira] [Commented] (KAFKA-5501) introduce async ZookeeperClient

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101268#comment-16101268 ] Onur Karaman commented on KAFKA-5501: - [~ijuma] I went ahead and reworded this ticket to be about

[jira] [Resolved] (KAFKA-5501) introduce async ZookeeperClient

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-5501. - Resolution: Fixed > introduce async ZookeeperClient > --- > >

[jira] [Updated] (KAFKA-5501) introduce async ZookeeperClient

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5501: Description: Synchronous zookeeper apis means that we wait an entire round trip before doing the

[jira] [Created] (KAFKA-5642) use async ZookeeperClient everywhere

Onur Karaman created KAFKA-5642: --- Summary: use async ZookeeperClient everywhere Key: KAFKA-5642 URL: https://issues.apache.org/jira/browse/KAFKA-5642 Project: Kafka Issue Type: Sub-task

[jira] [Updated] (KAFKA-5501) introduce async ZookeeperClient

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5501: Summary: introduce async ZookeeperClient (was: use async zookeeper apis everywhere) > introduce

[jira] [Commented] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101249#comment-16101249 ] huxihx commented on KAFKA-5641: --- [~ijuma] "The broker only processes one request at a time, so even if you

[jira] [Commented] (KAFKA-5501) use async zookeeper apis everywhere

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101244#comment-16101244 ] Ismael Juma commented on KAFKA-5501: The merged PR adds the async ZookeeperClient, but it doesn't

[jira] [Reopened] (KAFKA-5501) use async zookeeper apis everywhere

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-5501: > use async zookeeper apis everywhere > --- > > Key:

[jira] [Commented] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101231#comment-16101231 ] Ismael Juma commented on KAFKA-5641: The broker only processes one request at a time, so even if you

[jira] [Commented] (KAFKA-5501) use async zookeeper apis everywhere

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

[jira] [Resolved] (KAFKA-5501) use async zookeeper apis everywhere

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5501. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3427

[jira] [Commented] (KAFKA-4602) KIP-72 Allow putting a bound on memory consumed by Incoming requests

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