Hi All,
This KIP is accepted with 3 +1 binding votes(Luke, Christo, Jun, Satish)
and 2 +1 non-binding votes(Kamal, Omnia).
Thank you all for voting.
Abhijeet.
On Sat, Apr 27, 2024 at 5:50 AM Satish Duggana
wrote:
> Thanks Abhijeet for the KIP.
> +1 from me.
>
> ~Satish
>
> On Fri, 26 Apr
Chia-Ping Tsai created KAFKA-16640:
--
Summary: Replace TestUtils#resource by scala.util.Using
Key: KAFKA-16640
URL: https://issues.apache.org/jira/browse/KAFKA-16640
Project: Kafka
Issue
Chia-Ping Tsai created KAFKA-16639:
--
Summary: AsyncKafkaConsumer#close does not send heartbeat to leave
group
Key: KAFKA-16639
URL: https://issues.apache.org/jira/browse/KAFKA-16639
Project: Kafka
Omnia Ibrahim created KAFKA-16638:
-
Summary: Align the naming convention for config and default
variables in *Config classes
Key: KAFKA-16638
URL: https://issues.apache.org/jira/browse/KAFKA-16638
sanghyeok An created KAFKA-16637:
Summary: KIP-848 does not work well
Key: KAFKA-16637
URL: https://issues.apache.org/jira/browse/KAFKA-16637
Project: Kafka
Issue Type: Bug
Christo,
Updated the KIP with the remote fetch latency metric. Please take another
look!
--
Kamal
On Sun, Apr 28, 2024 at 12:23 PM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Hi Federico,
>
> Thanks for the suggestion! Updated the config name to "
>
Hi Federico,
Thanks for the suggestion! Updated the config name to "
remote.fetch.max.wait.ms".
Christo,
Good point. We don't have the remote-read latency metrics to measure the
performance of the remote read requests. I'll update the KIP to emit this
metric.
--
Kamal
On Sat, Apr 27, 2024 at
Heya Kamal,
I quite like the proposal and would support it!
However, today I don't think we have a metric which shows the latency of
fetch requests which are served from remote, am I wrong?
I looked at both
