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
[
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]
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
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
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
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.
> 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
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
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
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
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
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
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
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
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
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
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
17 matches
Mail list logo