Re: [DISCUSS] KIP-222 - Add "describe consumer group" to KafkaAdminClient

Great! I have added `listGroupOffsets` to the KIP. If there are no additional feedback, VOTE thread is already open. Cheers, Jorge El mar., 2 ene. 2018 a las 17:49, Gwen Shapira () escribió: > listGroups and listGroupOffsets will make it a snap to transition the > existing

Could give me the right to assign task to myself for kafka Jira

Hey, I want to assign this task [https://issues.apache.org/jira/browse/KAFKA-6422] to myself so I can fix that. But it looks like I don’t have the right to do so. Could you please grant me that right for that ? Thank you, Xin LI

Re: Could give me the right to assign task to myself for kafka Jira

Xin, I have added you to the contributor list, you can assign yourself to JIRAs now. CHeers, Guozhang On Sun, Jan 7, 2018 at 2:11 AM, Xin Li wrote: > Hey, > > I want to assign this task [https://issues.apache.org/ > jira/browse/KAFKA-6422] to myself so I can fix that. But

[jira] [Created] (KAFKA-6431) Lock contention in Purgatory

Ying Zheng created KAFKA-6431: - Summary: Lock contention in Purgatory Key: KAFKA-6431 URL: https://issues.apache.org/jira/browse/KAFKA-6431 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-6432) Lookup indices may cause unnecessary page fault

Ying Zheng created KAFKA-6432: - Summary: Lookup indices may cause unnecessary page fault Key: KAFKA-6432 URL: https://issues.apache.org/jira/browse/KAFKA-6432 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-6430) Improve Kafka GZip compression performance

Ying Zheng created KAFKA-6430: - Summary: Improve Kafka GZip compression performance Key: KAFKA-6430 URL: https://issues.apache.org/jira/browse/KAFKA-6430 Project: Kafka Issue Type: Improvement

Kafka 1.0 - corrupt index found

hi, after restart kafka 1.0/win64 does not work, plenty of corrupt index file - file could not open - is this zookeeper keeping it open ? or is this a known bug ? Peter

Re: Consumer client not able to receive messages when one of broker is pushed down in the cluster

Please suggest on how to avoid restart of Kafka Consumer Client on one of the broker fail down in the cluster. Or do we need to update the offset manually if we put back the failed broker in the cluster. On 5 January 2018 at 19:18, rAhul wrote: > Hi, > > I have a Apache