[jira] [Updated] (KAFKA-4128) Kafka broker losses messages when zookeeper session times out

[ https://issues.apache.org/jira/browse/KAFKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mazhar Shaikh updated KAFKA-4128: - Affects Version/s: 0.9.0.1 > Kafka broker losses messages when zookeeper session times out >

[jira] [Updated] (KAFKA-4128) Kafka broker losses messages when zookeeper session times out

[ https://issues.apache.org/jira/browse/KAFKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mazhar Shaikh updated KAFKA-4128: - Summary: Kafka broker losses messages when zookeeper session times out (was: Kafka broker loses

Re: Plans to improve SSL performance in Kafka, for 0.10.x?

On Tue, Sep 6, 2016 at 12:07 PM, Ismael Juma wrote: > On Tue, Sep 6, 2016 at 11:35 AM, Tom Crayford > wrote: > > > Our performance tests were run with the JVM producer and consumer, and we > > didn't notice any real slowdown on that side either when

[jira] [Created] (KAFKA-4128) Kafka broker loses messages when zookeeper session times out

Mazhar Shaikh created KAFKA-4128: Summary: Kafka broker loses messages when zookeeper session times out Key: KAFKA-4128 URL: https://issues.apache.org/jira/browse/KAFKA-4128 Project: Kafka

[jira] [Updated] (KAFKA-4124) Handle disk failures gracefully

[ https://issues.apache.org/jira/browse/KAFKA-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokul updated KAFKA-4124: - Description: Currently when a disk goes down, the broker also goes down with it. This causes too much reshuffle

[jira] [Updated] (KAFKA-4124) Handle disk failures gracefully

[ https://issues.apache.org/jira/browse/KAFKA-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokul updated KAFKA-4124: - Description: Currently when a disk goes down, the broker also goes down with it. Make the broker resilient to

[jira] [Updated] (KAFKA-4124) Handle disk failures gracefully

[ https://issues.apache.org/jira/browse/KAFKA-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokul updated KAFKA-4124: - Description: Currently when a disk goes down, the broker also goes down with it. Make the broker resilient to

Re: Plans to improve SSL performance in Kafka, for 0.10.x?

On Tue, Sep 6, 2016 at 11:35 AM, Tom Crayford wrote: > Our performance tests were run with the JVM producer and consumer, and we > didn't notice any real slowdown on that side either when enabling SSL. Just > to check the obvious: are your producers and consumers going over

Re: Plans to improve SSL performance in Kafka, for 0.10.x?

Hi Todd, Thanks for sharing your experience enabling TLS in your clusters. Very helpful. One comment below. On Sun, Sep 4, 2016 at 6:28 PM, Todd Palino wrote: > > Right now, we're specifically avoiding moving consume traffic to SSL, due > to the zero copy send issue. Now I've

[jira] [Comment Edited] (KAFKA-4119) Get topic offset with Kafka SSL

[ https://issues.apache.org/jira/browse/KAFKA-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467103#comment-15467103 ] zhang shuai edited comment on KAFKA-4119 at 9/6/16 10:53 AM: - Thinks for your

[jira] [Commented] (KAFKA-4119) Get topic offset with Kafka SSL

[ https://issues.apache.org/jira/browse/KAFKA-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467103#comment-15467103 ] zhang shuai commented on KAFKA-4119: Thinks for your reply. I used the new script

Re: Plans to improve SSL performance in Kafka, for 0.10.x?

> We have a single broker Kafka isn't really designed to run with a single broker setup. Whilst I doubt it impacts your problems here, you should immediately bump your broker count to 3 or more. Our performance tests were run with the JVM producer and consumer, and we didn't notice any real

[jira] [Commented] (KAFKA-4119) Get topic offset with Kafka SSL

[ https://issues.apache.org/jira/browse/KAFKA-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467026#comment-15467026 ] Rajini Sivaram commented on KAFKA-4119: --- You should use the newer ConsumerGroupCommand for the new

[jira] [Commented] (KAFKA-4121) Allow creating broker listeners from hostname

[ https://issues.apache.org/jira/browse/KAFKA-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466998#comment-15466998 ] Rajini Sivaram commented on KAFKA-4121: --- Advertised listeners can specify hostnames, the exception

[jira] [Resolved] (KAFKA-3779) Add the LRU cache for KTable.to() operator

[ https://issues.apache.org/jira/browse/KAFKA-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-3779. - Resolution: Not A Problem > Add the LRU cache for KTable.to() operator >

[jira] [Commented] (KAFKA-4111) broker compress data of certain size instead on a produce request

[ https://issues.apache.org/jira/browse/KAFKA-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466584#comment-15466584 ] Manikumar Reddy commented on KAFKA-4111: "compression.type" broker config property is applicable

Re: [DISCUSS] KIP-79 - ListOffsetRequest v1 and offsetForTime() method in new consumer.

Good write-up Qin, the API looks promising. I have one comment: 2016-09-03 5:20 GMT+02:00 Becket Qin : > The currently offsetsForTimes() API obviously does not support querying > multiple timestamps for the same partition. It doesn't seems a feature for > ListOffsetRequest

[jira] [Commented] (KAFKA-4109) kafka client send msg exception

[ https://issues.apache.org/jira/browse/KAFKA-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466570#comment-15466570 ] Manikumar Reddy commented on KAFKA-4109: Enable producer debug logs to get root cause of the

<    1   2