[DISCUSS] KIP-565: Using AclCommand,avoid call the global method loadcache in SimpleAclAuthorizer

Hello all, In the class Named AclCommand,configure SimpleAclAuthorizer,but no need call loadCache. now we have 20,000 topics in kafka cluster,everytime I run AclCommand,all these topics's Alcs need to be authed, it will be very slow. The purpose of this optimization is：we can choose to not load

[VOTE] KIP-547: Extend ConsumerInterceptor to allow modification of Consumer Commits

Hi all, I'd like to open a vote on KIP-547: Extend ConsumerInterceptor to allow modification of Consumer Commits This KIP is looking to improve the access to the Metadata included with Consumer Commits by adding a method to the ConsumerInterceptor that allows modification of the commit payloads.

Re: [DISCUSS] KIP-390: Allow fine-grained configuration for compression (Rebooted)

Hello Dongjin, I'm wondering if you have looked into the different implementor's buffer usage? So far as I read from the code: 1. LZ4 used a shared 64KB for decompression, and when reading it used ByteBuffer copy from the decompression buffer. 2. Snappy used shared uncompressed buffer, but when

Build failed in Jenkins: kafka-trunk-jdk11 #1097

See Changes: [manikumar.reddy] MINOR: Update introduction page in Kafka documentation -- [...truncated 2.84 MB...]

Re: [VOTE] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

Hello Brian, I looked at the new proposal again, and I'd like to reason about its rationale from the listed motivations in your wiki: 1) more RPCs: we may send metadata requests more frequently than appropriate. This is especially the case during producer start-up, where the more topics it needs

[VOTE] KIP-562: Allow fetching a key from a single partition rather than iterating over all the stores on an instance

Hello all, I'd like to propose a vote to serve keys from a specific partition-store instead of iterating over all the local stores of an instance to locate the key, as which happens currently. The full KIP is provided here:

Re: [VOTE] KIP-373: Allow users to create delegation tokens for other users

Hi Rajini, 1) I think we can to keep the conventions in the tool. As an addition we wouldn't have to retain certain characters (for creating the list). 2) Yes, so based on 1) and this --users changes to --user-principal (and accepts one single user principal). 3) Looking at it again probably

Re: [VOTE] KIP-515: Hardened TLS Configs to ZooKeeper

+1 (binding). Thanks for the KIP. On Mon, Jan 20, 2020 at 9:21 PM Rajini Sivaram wrote: > +1 (binding) > > Thanks for the KIP, Ron! > > Regards, > > Rajini > > > On Mon, Jan 20, 2020 at 3:36 PM Gwen Shapira wrote: > > > +1 (binding), this has been an on-going concern. Thank you for > >

[jira] [Created] (KAFKA-9456) EndToEndLatency: Add support for printing all latencies

Fábio Silva created KAFKA-9456: -- Summary: EndToEndLatency: Add support for printing all latencies Key: KAFKA-9456 URL: https://issues.apache.org/jira/browse/KAFKA-9456 Project: Kafka Issue

Re: [VOTE] KIP-515: Hardened TLS Configs to ZooKeeper

+1 (binding) Thanks for the KIP, Ron! Regards, Rajini On Mon, Jan 20, 2020 at 3:36 PM Gwen Shapira wrote: > +1 (binding), this has been an on-going concern. Thank you for > addressing this, Ron. > > On Mon, Jan 20, 2020 at 5:22 AM Ron Dagostino wrote: > > > > Hi everyone. I would like to

Re: [VOTE] KIP-515: Hardened TLS Configs to ZooKeeper

+1 (binding), this has been an on-going concern. Thank you for addressing this, Ron. On Mon, Jan 20, 2020 at 5:22 AM Ron Dagostino wrote: > > Hi everyone. I would like to start a vote on KIP-515: Enable ZK > client to use the new TLS supported authentication. > > The KIP is here: >

Re: [VOTE] KIP-515: Hardened TLS Configs to ZooKeeper

+1 (non-binding). Super +1 on this. -mitch On Mon, Jan 20, 2020 at 7:22 AM Ron Dagostino wrote: > > Hi everyone. I would like to start a vote on KIP-515: Enable ZK > client to use the new TLS supported authentication. > > The KIP is here: >

[VOTE] KIP-515: Hardened TLS Configs to ZooKeeper

Hi everyone. I would like to start a vote on KIP-515: Enable ZK client to use the new TLS supported authentication. The KIP is here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-515%3A+Enable+ZK+client+to+use+the+new+TLS+supported+authentication The discussion thread is here:

Re: [DISCUSS] KIP-515: Enable ZK client to use the new TLS supported authentication

Hi Rajini. Thanks. Yes, I’ll update the KIP, and then I’ll start the vote. Ron > On Jan 20, 2020, at 6:30 AM, Rajini Sivaram wrote: > > Hi Ron, > > Good point. Keystore and truststore configs (type/location/password) are > dynamically reconfigurable. A few of them like protocol,

Re: [DISCUSS] KIP-515: Enable ZK client to use the new TLS supported authentication

Hi Ron, Good point. Keystore and truststore configs (type/location/password) are dynamically reconfigurable. A few of them like protocol, enabled.protocols, cipher.suites and endpoint.identification.algorithm are not. But to keep it simple, it may be better not to inherit any of the SSL configs.

Re: [DISCUSS] : KIP-562: Allow fetching a key from a single partition rather than iterating over all the stores on an instance

Thanks John. If there are no other comments to be addressed, I will start a vote today so that we are on track for this release.~Navinder On Monday, January 20, 2020, 8:32 AM, John Roesler wrote: Thanks, Navinder, The Param object looks a bit different than I would have done, but it

Re: [DISCUSS] KIP-552: Add new cached authorizer:change the dim of cache

Hi Steven, Because of the change in KIP numbers, the KIP numbers above are misleading. The subject says of the discussion thread says KIP-552 and the link says KIP-553. But it is actually none of those since the KIP is now KIP-565. A couple of questions regarding the KIP: 1) Do we bound the