[jira] [Resolved] (KAFKA-5809) when zookeeper set acl on path /. then kafka can't connect zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5809. -- Resolution: Won't Fix either we need to remove the acls on zk node acls or enable Zk SASL authenticatio

[jira] [Created] (KAFKA-6592) NullPointerException thrown when executing ConsoleCosumer with deserializer set to `WindowedDeserializer`

huxihx created KAFKA-6592: - Summary: NullPointerException thrown when executing ConsoleCosumer with deserializer set to `WindowedDeserializer` Key: KAFKA-6592 URL: https://issues.apache.org/jira/browse/KAFKA-6592

[DISCUSS] KIP-263: Allow broker to skip sanity check of inactive segments on broker startup

Hi all, I have created KIP-263: Allow broker to skip sanity check of inactive segments on broker startup. See https://cwiki.apache.org/confluence/display/KAFKA/KIP-263%3A+Allow+broker+to+skip+sanity+check+of+inactive+segments+on+broker+startup . This KIP provides a way to significantly reduce tim

Build failed in Jenkins: kafka-trunk-jdk7 #3213

See Changes: [github] MINOR: fixes lgtm.com warnings (#4582) -- [...truncated 120.44 KB...] unit.kafka.admin.DeleteConsumerGroupTest > testDeleteWithShortInitialization S

Build failed in Jenkins: kafka-trunk-jdk8 #2438

See Changes: [github] MINOR: fixes lgtm.com warnings (#4582) -- [...truncated 3.92 MB...] org.apache.kafka.streams.processor.internals.ProcessorStateManagerTest > testRe

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hey Matthias, Thanks for the comments. I think when we compact topics, we only delete those messages (when there is later message with the same key) and we do not change offset of a given message. As long as offsets of existing messages are not changes, I think the KIP should still work in the se

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hey Jay, Thanks for the comment! I have not specifically thought about how this works with Streams and Connect. The current KIP w.r.t. the interface that our producer and consumer exposes to the user. It ensures that if there are two messages with the same key produced by the same producer, say m

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hey Allen, Thanks for your comment. I will comment inline. On Thu, Feb 22, 2018 at 3:05 PM, Allen Wang wrote: > Overall this is a very useful feature. With this we can finally scale keyed > messages. > > +1 on the ability to remove partitions. This will greatly increase Kafka's > scalability in

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hey Jun, Yeah I think this definitely makes sense. I have updated the KIP to support partition deletion and also added callback as you previously suggested. Can you take another look? Thanks! Dong On Thu, Feb 22, 2018 at 11:52 AM, Jun Rao wrote: > Hi, Dong, > > Regarding deleting partitions, G

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hey Gwen, Thanks for the use-case. This is certainly useful. I have updated the KIP to allow partition deletion as well. Dong On Wed, Feb 21, 2018 at 9:49 PM, Gwen Shapira wrote: > Re: Why would anyone want to delete partitions: > > Imagine a system that is built to handle 200K events per sec

[jira] [Created] (KAFKA-6591) Move check for super user in SimpleAclProvider before ACL evaluation

Sönke Liebau created KAFKA-6591: --- Summary: Move check for super user in SimpleAclProvider before ACL evaluation Key: KAFKA-6591 URL: https://issues.apache.org/jira/browse/KAFKA-6591 Project: Kafka