[jira] [Created] (KAFKA-13474) Regression in dynamic update of client-side SSL factory

2021-11-23 Thread Igor Shipenkov (Jira)
Igor Shipenkov created KAFKA-13474: -- Summary: Regression in dynamic update of client-side SSL factory Key: KAFKA-13474 URL: https://issues.apache.org/jira/browse/KAFKA-13474 Project: Kafka I

[jira] [Resolved] (KAFKA-13117) After processors, migrate TupleForwarder and CacheFlushListener

2021-11-23 Thread Jorge Esteban Quilcate Otoya (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-13117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Esteban Quilcate Otoya resolved KAFKA-13117. -- Resolution: Fixed [https://github.com/apache/kafka/pull/11481]

Re: [VOTE] KIP-798 Add possibility to write kafka headers in Kafka Console Producer

2021-11-23 Thread Luke Chen
Hi Florin, I'm not a committer, but yes, this vote be concluded now. Thank you. Luke On Wed, Nov 24, 2021 at 3:08 AM Florin Akermann wrote: > Thanks all. > > The 72h window is through. > > @Comitters can this vote be concluded? > > The vote on KIP-798 would pass with: > 4 binding +1 > 1 non-bin

[jira] [Created] (KAFKA-13473) Log cleaner Dynamic configs aren't applied after a restart

2021-11-23 Thread Tim Patterson (Jira)
Tim Patterson created KAFKA-13473: - Summary: Log cleaner Dynamic configs aren't applied after a restart Key: KAFKA-13473 URL: https://issues.apache.org/jira/browse/KAFKA-13473 Project: Kafka

[DISCUSS] KIP-801: Implement an Authorizer that stores metadata in __cluster_metadata

2021-11-23 Thread Colin McCabe
Hi all, I have written a new KIP describing an Authorizer that stores data in the __cluster_metadata topic. It is designed to be used in KRaft mode. Please take a look here: https://cwiki.apache.org/confluence/x/h5KqCw best, Colin

Re: [VOTE] KIP-798 Add possibility to write kafka headers in Kafka Console Producer

2021-11-23 Thread Florin Akermann
Thanks all. The 72h window is through. @Comitters can this vote be concluded? The vote on KIP-798 would pass with: 4 binding +1 1 non-binding +1 no vetoes Thanks, Florin On Tue, 23 Nov 2021 at 06:59, Luke Chen wrote: > Hi Florin, > Thanks for the update! > > +1 (non-binding) > > Thank you.

Re: [DISCUSS] KIP-782: Expandable batch size in producer

2021-11-23 Thread Artem Livshits
> maybe I can firstly decrease the "batch.max.size" to 32KB I think 32KB is too small. With 5 in-flight and 100ms latency we can produce 1.6MB/s per partition. With 256KB we can produce 12.8MB/s per partition. We should probably set up some testing and see if 256KB has problems. To illustrate

Re: [DISCUSS] KIP-714: Client metrics and observability

2021-11-23 Thread Bob Barrett
Hi Magnus, Thanks for the thorough KIP, this seems very useful. Would it make sense to include the request type as a label for the `client.request.success`, `client.request.errors` and `client.request.rtt` metrics? I think it would be very useful to see which specific requests are succeeding and

Re: [DISCUSS] Apache Kafka 3.1.0 release

2021-11-23 Thread Mickael Maison
Hi David, Can we also consider https://issues.apache.org/jira/browse/KAFKA-13397? It's essentially a regression but in a very specific case. To hit it, you must be running MirrorMaker in dedicated mode and have changed the separator of the default replication policy. Thanks, Mickael On Tue, Nov

Re: KIP-769: Connect API to retrieve connector configuration definitions

2021-11-23 Thread Chris Egerton
Hi Mickael, I think the increase in scope here is great and the added value certainly justifies the proposed changes. I have some thoughts but overall I like the direction this is going in now. 1. The new /plugins endpoint is described as containing "all plugins that are Connectors, Transformatio

Re: KIP-769: Connect API to retrieve connector configuration definitions

2021-11-23 Thread Mickael Maison
Thanks all for the feedback! Chris, I agree that fixing the current endpoint helps a lot. Thanks for raising these JIRAs and submitting a PR! However thinking about the issue further, I decided to expand the scope of the KIP to cover all user-visible plugins. In practice, users want to know about

Re: [DISCUSS] Apache Kafka 3.1.0 release

2021-11-23 Thread David Jacot
Hi Ron, Thank you for reaching out about this. While this is clearly not a regression, I agree with including it in 3.1 in order to have proper and correct configuration constraints for KRaft. You can proceed. Cheers, David On Tue, Nov 23, 2021 at 2:55 PM Ron Dagostino wrote: > > Hi David. I w

Re: [DISCUSS] Apache Kafka 3.1.0 release

2021-11-23 Thread Ron Dagostino
Hi David. I would like to nominate https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13456 "Tighten KRaft config checks/constraints" as a 3.1.0 blocker. The existing configuration constraints/checks related to KRaft currently do not eliminate certain illegal configuration combinations. T

Re: [VOTE] KIP-780: Support fine-grained compression options

2021-11-23 Thread Dongjin Lee
Bumping up the voting thread. As of present: - binding: 0 - non-binding: 1 (Luke) Thanks, Dongjin On Wed, Oct 27, 2021 at 9:47 PM Luke Chen wrote: > Hi Dongjin, > Thanks for the KIP. > +1 (non-binding) > > Luke > > On Wed, Oct 27, 2021 at 8:44 PM Dongjin Lee wrote: > > > Bumping up the voting

Re: [DISCUSS] KIP-719: Add Log4J2 Appender

2021-11-23 Thread Dongjin Lee
Hi Mickael, I also thought over the issue thoroughly and would like to propose a minor change to your proposal: 1. Deprecate log4j-appender now 2. Document how to migrate into logging-log4j2 3. (Changed) Replace the log4j-appender (in turn log4j 1.x) dependencies in tools, trogdor, and shell and

Re: [DISCUSS] Apache Kafka 3.1.0 release

2021-11-23 Thread David Jacot
Hi Chris, Thanks for reporting both issues. As both are regressions, I do agree that they are blockers and that we would fix them for 3.1. Cheers, David On Mon, Nov 22, 2021 at 10:50 PM Chris Egerton wrote: > > Hi David, > > I have another blocker to propose. KAFKA-13472 ( > https://issues.apac

Re: [DISCUSS] KIP-782: Expandable batch size in producer

2021-11-23 Thread Luke Chen
Hi Tom, Thanks for your comments. And thanks for Artem's explanation. Below is my response: > Currently because buffers are allocated using batch.size it means we can handle records that are that large (e.g. one big record per batch). Doesn't the introduction of smaller buffer sizes (batch.initial