, and a patch is already
> available. Do you want to include the patch in 4.0.1, or should I do the
> cherry-pick after 4.0.1 is released?
>
> Best,
> Chia-Ping
>
>
> On 2025/09/11 10:09:00 Christo Lolov wrote:
> > Hello Kafka users, developers and client-developers,
>
[
https://issues.apache.org/jira/browse/KAFKA-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-8202.
--
Resolution: Fixed
> StackOverflowError on producer when splitting batc
[
https://issues.apache.org/jira/browse/KAFKA-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-8350.
--
Resolution: Fixed
> Splitting batches should consider topic-level message s
Hello Kafka users, developers and client-developers,
This is the third candidate for release of Apache Kafka 4.0.1.
Since this is a patch version it contains the bug fixes outlined in the
release notes below!
Release notes for the 4.0.1 release:
https://dist.apache.org/repos/dist/dev/kafka/4.0.1
Hello!
I know I haven't completed the 4.0.1 release yet, but I am quite keen on
trying to be the release manager for a minor release in the future.
Obviously, I am happy for anybody else with more experience to give this a
go first, I just wanted to put my hand up in case we lack other volunteers.
t;
> - https://github.com/apache/kafka/pull/20470
> - https://github.com/apache/kafka/pull/20484
> - https://github.com/apache/kafka-site/pull/721
> - https://github.com/apache/kafka/pull/20506
>
>
> -Matthias
>
>
> On 9/3/25 9:13 AM, Christo Lolov wrote:
> > Heya M
e should get a new
> RC? Getting a new RC might be simplest (even if the bug is not a
> regression), instead of doing a 4.0.2 bug-fix release as follow up.
>
> Thoughts?
>
> Thanks a lot,
>-Matthias
>
>
> On 9/3/25 8:14 AM, Christo Lolov wrote:
> > Hello!
> >
ionality
> - Verified signatures and checksums of the downloaded artifacts
>
> +1 (non-binding)
>
> Thanks for the release!
> Hong-Yi Chen
>
> Christo Lolov 於 2025年8月19日 週二 下午11:43寫道：
>
> > Hello Kafka users, developers and client-developers,
> >
> > This is the
ve missed the steps
> > in
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34840886#ReleaseProcess-CreateGraalVMBasedNativeApacheKafkaDockerArtifact(Forversions
> > >=3.8.0)
> >
> > Thanks,
> > Mickael
> >
> > On Tue, Aug 19, 2025 a
Hello!
I carried out the following checks:
* Built Kafka from source using JDK 24
* Ran unit tests
* Validated signatures and checksums
* Ran the quickstart tutorial
* Tested disabling and reenabling of ELR
* Tested ELR defaulting to enabled after an upgrade from a 4.0.0 cluster to
4.1.0
* Tested
Hello Kafka users, developers and client-developers,
This is the second candidate for release of Apache Kafka 4.0.1.
Since this is a patch version it contains the bug fixes outlined in the
release notes below!
Release notes for the 4.0.1 release:
https://dist.apache.org/repos/dist/dev/kafka/4.0.
you take a look at https://github.com/apache/kafka/pull/20273 and
> > let us know what you think?
> >
> > Thanks.
> >
> > -Matthias
> >
> > On 7/25/25 1:51 AM, Christo Lolov wrote:
> > > Hello Kafka users, developers and client-developers,
> &
Heya!
I tested creating a cluster using the binary tgz. Furthermore, I went
through the enabling, producing, consuming, and disabling of queues.
Lastly, I carried out the same steps on both Docker images.
I went through the JavaDocs and clicked on links to confirm they work.
I chose artifacts at
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka 4.0.1.
Since this is a patch version it contains the bug fixes outlined in the
release notes below!
Release notes for the 4.0.1 release:
https://dist.apache.org/repos/dist/dev/kafka/4.0.1
Hello,
The 23rd is now drawing to an end. I am slightly behind schedule, but will
be continuing with creating the artifacts tomorrow!
Best,
Christo
On Mon, 30 Jun 2025 at 12:31, Christo Lolov wrote:
> Hello!
>
> I have volunteered to be the release manager for the 4.0.1 release.
&
Hello!
I have volunteered to be the release manager for the 4.0.1 release.
I have put together the release plan at
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+4.0.1
The first release candidate will be cut on the 23rd of July (~3 weeks from
the date of this email). Feel free to
Hello!
I would like to volunteer as a release manager for 4.0.1! I haven't done
this before so I will most likely reach out for help if accepted :)
Best,
Christo
On Wed, 25 Jun 2025 at 16:48, Josep Prat
wrote:
> But of course, Vivekanand, you are more than welcome to help out testing
> and val
Hello!
Apologies for coming late to the party. I think this is a great idea and
don't see why we can't try it out in practice!
+1 (binding)
Best,
Christo
On Tue, 29 Apr 2025 at 15:16, Andrew Schofield <
andrew_schofield_j...@outlook.com> wrote:
> Thanks for the KIP, Ivan.
>
> +1 (binding)
>
>
Hello!
It is great to see another proposal on the same topic, but optimising for
different scenarios, so thanks a lot for the effort put in this!
I have a few questions and statements in no particular order.
If you use acks=-1 (acks=all) then an acknowledgement can only be sent to
the producer i
Hello!
I want to start with saying that this is a big and impressive undertaking
and I am really excited to see its progression! I am posting my initial
comments in this thread, but they span a few of the child KIPs. Let me know
which questions you would like to move elsewhere. I understand that y
Congratulations!
On Thu, 10 Apr 2025 at 18:22, David Arthur wrote:
> Congrats!!
>
> David Arthur
>
>
> On Thu, Apr 10, 2025 at 12:43 TengYao Chi wrote:
>
> > Thank you very much everyone!!
> >
> > I truly appreciate all your reviews, guidance, and discussions on my code
> > contributions.
> > Y
[
https://issues.apache.org/jira/browse/KAFKA-18694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-18694.
---
Resolution: Fixed
> Migrate suitable classes to recorods in coordinator-common mod
[
https://issues.apache.org/jira/browse/KAFKA-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-18705.
---
Resolution: Fixed
> Move ConfigRepository to metadata mod
[
https://issues.apache.org/jira/browse/KAFKA-18698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-18698.
---
Resolution: Fixed
> Migrate suitable classes to records in server and server-common modu
[
https://issues.apache.org/jira/browse/KAFKA-18545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-18545.
---
Resolution: Fixed
> Remove Zookeeper logic from LogMana
[
https://issues.apache.org/jira/browse/KAFKA-18685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-18685.
---
Resolution: Fixed
> Cleanup DynamicLogConfig construc
Heya David,
Thanks a lot for this!
Building on top of Chris's questions - does including only a subset of the
stages in the merge queue mean that while subsequent stages (i.e. tests)
can run in parallel-ish across PRs they will contain trunk + set of PRs
ahead of this one which passed the stage i
[
https://issues.apache.org/jira/browse/KAFKA-18598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-18598.
---
Resolution: Fixed
The PR has been reviewed and merged both in trunk and in 4.0
> Rem
[
https://issues.apache.org/jira/browse/KAFKA-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-18595.
---
Resolution: Fixed
The PR has been reviewed and merged both in trunk and 4.0
> Rem
Congratulations Andrew, well deserved!
On Mon, 2 Dec 2024 at 16:36, Josep Prat wrote:
> Congrats Andrew!
>
>
> On Mon, Dec 2, 2024 at 5:33 PM Mickael Maison
> wrote:
>
> > Congratulations Andrew!
> >
> > Thanks,
> > Mickael
> >
> > On Mon, Dec 2, 2024 at 5:27 PM Kuan Po Tseng
> wrote:
> > >
>
Heya,
Apologies for the delay. You have my +1 vote as well! I am excited to see
this making it in 4.0
Best,
Christo
On Wed, 6 Nov 2024 at 09:43, Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Hi all,
>
> The KIP is passed with 3 (+1) binding votes. Thanks everyone!
>
> Binding
Heya,
I have ran a few times into issues which required adjustment of the thread
pools and having to carry out a rolling restart was cumbersome.
+1 (binding) for the change!
Best,
Christo
On Thu, 7 Nov 2024 at 16:17, Satish Duggana
wrote:
> +1 (binding)
>
> On Thu, 7 Nov 2024 at 13:55, Federi
Heya,
Apologies for the delay. I have been thinking about this problem recently
as well and while I believe storing a boolean in the metadata is good, I
think we can do better by introducing a new method to the RLMM along the
lines of
Optional
nextRemoteLogSegmentMetadataWithTxnIndex(TopicIdParti
Many congratulations Kamal! Very well deserved!
On Tue, 1 Oct 2024 at 08:21, Jorge Esteban Quilcate Otoya <
quilcate.jo...@gmail.com> wrote:
> Congrats Kamal!!
>
> On Tue 1. Oct 2024 at 7.54, Kamal Chandraprakash <
> kamal.chandraprak...@gmail.com> wrote:
>
> > Thank you all for your warm wishes!
Hello,
I have filed https://issues.apache.org/jira/browse/KAFKA-17584 as a
blocker. While it has not been introduced by a KIP, I think this has
durability implications and needs to be addressed immediately.
Let me know if you disagree!
Best,
Christo
On Thu, 19 Sept 2024 at 16:01, José Armando G
Christo Lolov created KAFKA-17584:
-
Summary: Changing dynamic configurations resets retention
Key: KAFKA-17584
URL: https://issues.apache.org/jira/browse/KAFKA-17584
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-17579.
---
Resolution: Fixed
> Dynamic LogCleaner configurations are not picked up upon rest
Christo Lolov created KAFKA-17579:
-
Summary: Dynamic LogCleaner configurations are not picked up upon
restart
Key: KAFKA-17579
URL: https://issues.apache.org/jira/browse/KAFKA-17579
Project: Kafka
Hello!
Apologies for the late arrival. I read through the KIP and the discussion
thread and I have no concerns with the proposed approach.
This is a great improvement!
+1 from me.
Best,
Christo
On Fri, 23 Aug 2024 at 02:50, Luke Chen wrote:
> +1 from me.
>
> Thanks.
>
> On Thu, Aug 22, 2024 a
ture. However, I
> am
> >> a bit sceptical on the ZK part of the story. The 3.8 release is supposed
> >> to
> >> be the last one supporting ZK so I don't really see how we could bring
> it
> >> to ZK, knowing that we don't plan to do a 3.9 release (cur
ood if you could add that into the KIP.
> >
> > Otherwise, LGTM.
> >
> > Thank you.
> > Luke
> >
> > On Mon, May 13, 2024 at 11:55 PM Christo Lolov
> > wrote:
> >
> > > Heya!
> > >
> > > re Kamal - Okay, I believe I un
Christo Lolov created KAFKA-17031:
-
Summary: Make configurations public
Key: KAFKA-17031
URL: https://issues.apache.org/jira/browse/KAFKA-17031
Project: Kafka
Issue Type: Sub-task
Christo Lolov created KAFKA-16857:
-
Summary: Zookeeper - Add new ZNodes
Key: KAFKA-16857
URL: https://issues.apache.org/jira/browse/KAFKA-16857
Project: Kafka
Issue Type: Sub-task
Christo Lolov created KAFKA-16856:
-
Summary: Zookeeper - Add new exception
Key: KAFKA-16856
URL: https://issues.apache.org/jira/browse/KAFKA-16856
Project: Kafka
Issue Type: Sub-task
Christo Lolov created KAFKA-16855:
-
Summary: KRaft - Wire replaying a TopicRecord
Key: KAFKA-16855
URL: https://issues.apache.org/jira/browse/KAFKA-16855
Project: Kafka
Issue Type: Sub-task
Christo Lolov created KAFKA-16854:
-
Summary: Zookeeper - Add v5 of StopReplica
Key: KAFKA-16854
URL: https://issues.apache.org/jira/browse/KAFKA-16854
Project: Kafka
Issue Type: Sub-task
Christo Lolov created KAFKA-16853:
-
Summary: Split RemoteLogManagerScheduledThreadPool
Key: KAFKA-16853
URL: https://issues.apache.org/jira/browse/KAFKA-16853
Project: Kafka
Issue Type: Sub
Christo Lolov created KAFKA-16851:
-
Summary: Add remote.log.disable.policy
Key: KAFKA-16851
URL: https://issues.apache.org/jira/browse/KAFKA-16851
Project: Kafka
Issue Type: Sub-task
Christo Lolov created KAFKA-16852:
-
Summary: Add *.thread.pool.size
Key: KAFKA-16852
URL: https://issues.apache.org/jira/browse/KAFKA-16852
Project: Kafka
Issue Type: Sub-task
Christo Lolov created KAFKA-16850:
-
Summary: KRaft - Add v2 of TopicRecord
Key: KAFKA-16850
URL: https://issues.apache.org/jira/browse/KAFKA-16850
Project: Kafka
Issue Type: Sub-task
Hello!
I am closing this vote as ACCEPTED with 3 binding +1 (Luke, Chia-Ping and
Satish) and 1 non-binding +1 (Kamal) - thank you for the reviews!
Realistically, I don't think I have the bandwidth to get this in 3.8.0.
Due to this, I will mark tentatively the Zookeeper part for 3.9 if the
communi
Christo Lolov created KAFKA-16790:
-
Summary: Calls to RemoteLogManager are made before it is configured
Key: KAFKA-16790
URL: https://issues.apache.org/jira/browse/KAFKA-16790
Project: Kafka
Heya!
I would like to start a vote on KIP-950: Tiered Storage Disablement in
order to catch the last Kafka release targeting Zookeeper -
https://cwiki.apache.org/confluence/display/KAFKA/KIP-950%3A++Tiered+Storage+Disablement
Best,
Christo
ink infinite retries is a good idea since if a broker is down
> forever, this request will never complete.
> You mentioned the existing topic deletion is using the similar pattern, how
> does it handle this issue?
>
> Thanks.
> Luke
>
> On Thu, May 9, 2024 at 9:21 PM Christo Lol
ller, not listening for
> changes in
> >>>> ZK.
> >>>>
> >>>> 3. In the KRaft handler steps, you said:
> >>>> "The controller also updates the Topic metadata to increment the
> >>>> tiered_epoch and update the tiere
Heya Kamal,
Thanks for the KIP and the answers in the discussion!
+1 from me :)
Best,
Christo
On Thu, 9 May 2024 at 11:11, Federico Valeri wrote:
> +1 non binding
>
> Thanks
>
> On Thu, May 9, 2024 at 12:05 PM Luke Chen wrote:
> >
> > Hi Kamal,
> >
> > Thanks for the KIP!
> > +1 from me.
> >
Heya!
Is it difficult to instead add the metric at
kafka.network:type=RequestMetrics,name=TieredStorageMs (or some other
name=*)? Alternatively, if it is difficult to add it there, is it possible
to add 2 metrics, one at the RequestMetrics level (even if it is
total-time-ms - (all other times)) an
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
https://github.com/clolov/kafka/blob/trunk/core/src/main/scala/kafka/network/RequestChanne
Heya Abhijeet,
Thanks a lot for pushing this forward, especially with the explanation of
EARLIEST_PENDING_UPLOAD_OFFSET_TIMESTAMP!
+1 from me :)
Best,
Christo
On Fri, 26 Apr 2024 at 12:50, Luke Chen wrote:
> Hi Abhijeet,
>
> Thanks for the KIP.
> +1 from me.
>
> Thanks.
> Luke
>
> On Fri, Apr
Congratulations Igor :) !
On Thu, 25 Apr 2024 at 17:07, Igor Soarez wrote:
> Thanks everyone, I'm very honoured to join!
>
> --
> Igor
>
Heya Nikhil,
Thanks for the proposal, as mentioned before it makes sense to me!
+1 (binding)
Best,
Christo
On Sat, 20 Apr 2024 at 00:25, Justine Olshan
wrote:
> Hey Nikhil,
>
> I meant to comment on the discussion thread, but my draft took so long, you
> opened the vote.
>
> Regardless, I jus
would have to use already existing methods
Let me know if there are any new comments or I have missed something!
Best,
Christo
On Mon, 15 Apr 2024 at 12:40, Christo Lolov wrote:
> Heya Doguscan,
>
> I believe that the state of the world after this KIP will be the following:
>
>
on from DisableRemoteTopic
>> within the StopReplicas API which will then disappear in KRaft world as it
>> is already scheduled for deprecation. What do you think?
>>
>> Sounds good to me.
>>
>> Thanks.
>> Luke
>>
>> On Tue, Apr 9, 2024 at 6:46 PM
Heya Nikhil,
Thank you for raising this KIP!
Your proposal makes sense to me. In essence you are saying that the
permission required by WriteTxnMarkers should be the same as for CreateAcls
and DeleteAcls, which is reasonable. If we trust an administrator to assign
the correct permissions then we
Congratulations, Greg :)
On Mon, 15 Apr 2024 at 07:34, Zhisheng Zhang <31791909...@gmail.com> wrote:
> Congratulations Greg!
>
>
> Manikumar 于2024年4月15日周一 13:49写道：
>
> > Congratulations, Greg.
> >
> > On Mon, Apr 15, 2024 at 11:18 AM Bruno Cadonna
> wrote:
> > >
> > > Congratulations, Greg!
> >
tarting doing unexpected upload/fetch tasks, right?
> I agree we should make sure in ZK mode, all brokers are completed the
> stopPartitions before moving to "Disabled" state because ZK node watcher is
> working in a separate thread. But not sure about KRaft mode.
>
> Thanks
Christo Lolov created KAFKA-16480:
-
Summary: ListOffsets change should have an associated API/IBP
version update
Key: KAFKA-16480
URL: https://issues.apache.org/jira/browse/KAFKA-16480
Project: Kafka
>
> > Hi Christo,
> >
> > Thanks for reviewing the KIP.
> >
> > The follower needs the earliest-pending-upload-offset (and the
> > corresponding leader epoch) from the leader.
> > This is the first offset the follower will have locally.
> >
> &
ending Controller -> Broker RPCs. In fact, KIP-631 deprecated these
> > RPCs.
> > > >
> > > > I will come up with some recommendations on how we could improve that
> > > one but until then, @Luke please feel free to review the KIP.
> > > >
> > > > @Satish, if we wan
Heya!
First of all, thank you very much for the proposal, you have explained the
problem you want solved very well - I think a faster bootstrap of an empty
replica is definitely an improvement!
For my understanding, which concrete offset do you want the leader to give
back to a follower - earlies
Thank you everyone!
It wouldn't have been possible without quite a lot of reviews and extremely
helpful inputs from you and the rest of the community! I am looking forward
to working more closely with you going forward :)
On Tue, 26 Mar 2024 at 14:31, Kirk True wrote:
> Congratulations Christo!
Duggana
> wrote:
>
> > Hi Christo,
> > Thanks for volunteering to contribute to the KIP discussion. I suggest
> > considering this KIP for both ZK and KRaft as it will be helpful for
> > this feature to be available in 3.8.0 running with ZK clusters.
> >
> > Thank
Hello!
I volunteer to get this KIP moving forward and implemented in Apache Kafka
3.8.
I have caught up with Mehari offline and we have agreed that given Apache
Kafka 4.0 being around the corner we would like to propose this feature
only for KRaft clusters.
Any and all reviews and comments are w
Christo Lolov created KAFKA-16154:
-
Summary: Make broker changes to return an offset for
LATEST_TIERED_TIMESTAMP
Key: KAFKA-16154
URL: https://issues.apache.org/jira/browse/KAFKA-16154
Project: Kafka
11 Jan 2024 at 17:52, Divij Vaidya
> > > > wrote:
> > > > >
> > > > > +1 (binding)
> > > > >
> > > > > Divij Vaidya
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Dec 26, 2023
[
https://issues.apache.org/jira/browse/KAFKA-15734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-15734.
---
Resolution: Fixed
> KRaft support in BaseConsumerT
, if the timestamp greater than recently
> committed record timestamp is given.]"
>
> WDYT?
>
> Thanks.
> Luke
>
> On Mon, Jan 15, 2024 at 6:46 PM Christo Lolov
> wrote:
>
> > Heya Luke,
> >
> > Thank for the question! I have expanded in the KIP -
gt; Thank you for making the change Christo. It looks good to me.
> >
> > --
> > Divij Vaidya
> >
> >
> >
> > On Thu, Jan 11, 2024 at 11:19 AM Christo Lolov
> > wrote:
> >
> > > Thank you Divij!
> > >
> > > I hav
;
> --
> Divij Vaidya
>
>
>
> On Tue, Nov 21, 2023 at 2:19 PM Christo Lolov
> wrote:
>
> > Heya!
> >
> > Thanks a lot for this. I have updated the KIP to include exposing the
> > tiered-offset as well. Let me know whether the Public Interfaces section
> >
Heya all!
KIP-1005 (
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1005%3A+Expose+EarliestLocalOffset+and+TieredOffset)
has been open for around a month with no further comments - I would like to
start a voting round on it!
Best,
Christo
Heya Kamal,
The proposed change makes sense to me as it will be a more explicit
behaviour than what Kafka does today - I am happy with it!
+1 (non-binding) from me
Best,
Christo
On Tue, 12 Dec 2023 at 09:01, Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Hi,
>
> I would like t
Christo Lolov created KAFKA-16002:
-
Summary: Implement RemoteCopyLagSegments, RemoteDeleteLagBytes and
RemoteDeleteLagSegments
Key: KAFKA-16002
URL: https://issues.apache.org/jira/browse/KAFKA-16002
Kamal Chandraprakash
> > wrote:
> > >
> > > +1 (non-binding). Thanks for the KIP!
> > >
> > > On Tue, Nov 21, 2023, 03:04 Divij Vaidya
> > wrote:
> > >
> > > > + 1 (binding)
> > > >
> > >
Christo Lolov created KAFKA-15883:
-
Summary: Implement RemoteCopyLagBytes
Key: KAFKA-15883
URL: https://issues.apache.org/jira/browse/KAFKA-15883
Project: Kafka
Issue Type: Sub-task
> highest-copied-remote-offset via
> > GetOffsetShell tool? This will be useful during the debugging session.
> >
> >
> > On Mon, Nov 20, 2023 at 5:38 PM Christo Lolov
> > wrote:
> >
> > > Hello all!
> > >
> > > I would like to start
Hello all!
I would like to start a discussion for
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1005%3A+Add+EarliestLocalOffset+to+GetOffsetShell
.
A new offset called local log start offset was introduced as part of
KIP-405: Kafka Tiered Storage. KIP-1005 aims to expose this offset by
ch
Hello all!
Now that the discussion for KIP-963 has winded down, I would like to open
it for a vote targeting 3.7.0 as the release. You can find the current
version of the KIP at
https://cwiki.apache.org/confluence/display/KAFKA/KIP-963%3A+Additional+metrics+in+Tiered+Storage
Best,
Christo
ake those fine grained remote fetch flow sequence
> metrics separately later?
>
> Thanks,
> Satish.
>
> On Tue, 14 Nov 2023 at 22:07, Christo Lolov
> wrote:
> >
> > Heya everyone,
> >
> > Apologies for the delay in my response and thank you very much for all
I find the record-based lag less useful as records
> > > can't
> > > > > be relied as a stable unit of measure. So, if we can keep bytes-
> and
> > > > > segment-based lag, LGTM.
> > > > > 3.4. Agree, these metrics should be on the broker
other internals) to have some metrics attached -- maybe if you
> could shared scenarios where this metrics would be useful would be helpful.
>
> 7. On the metrics naming: not sure the `Total*` prefix is really needed or
> adds meaning. When I found it useful is when there are related metr
metrics and their granularity!
Best,
Christo
On Fri, 13 Oct 2023 at 10:14, Christo Lolov wrote:
> Heya Gantigmaa,
>
> Apologies for the (very) late reply!
>
> Now that 3.6 has been released and reviewers have a bit more time I will
> be picking up this KIP again. I am more
Christo Lolov created KAFKA-15660:
-
Summary: File-based Tiered Storage should delete folders upon
topic deletion
Key: KAFKA-15660
URL: https://issues.apache.org/jira/browse/KAFKA-15660
Project: Kafka
ose metrics
> were not mentioned in the original KIP-405 or KIP-930. Do you think these
> would make sense to be added to this KIP and get included in the
> discussion?
>
> Regards,
> Gantigmaa
>
> On Wed, Aug 9, 2023 at 1:53 PM Christo Lolov
> wrote:
>
> > Heya
[
https://issues.apache.org/jira/browse/KAFKA-15385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-15385.
---
Resolution: Duplicate
Closing this in favour of https://issues.apache.org/jira/browse/KAFKA
[
https://issues.apache.org/jira/browse/KAFKA-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-15382.
---
Resolution: Duplicate
Closing this ticket in favour of
https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/KAFKA-15383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-15383.
---
Resolution: Duplicate
Closing this ticket in favour of
https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/KAFKA-15384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-15384.
---
Resolution: Fixed
Closing this ticket in favour of
https://issues.apache.org/jira/browse
Heya,
I have compiled and ran the test target successfully for the 3.6.0-rc0
branch on:
Java 11, Scala 2.13 - ARM
Java 17, Scala 2.13 - ARM
Java 20, Scala 2.18 - ARM
Java 11, Scala 2.13 - Intel x86
Java 17, Scala 2.13 - Intel x86
Java 20, Scala 2.13 - Intel x86
I will update the Zookeeper KIP ti
[
https://issues.apache.org/jira/browse/KAFKA-15399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-15399.
---
Resolution: Fixed
> Enable OffloadAndConsumeFromLeader t
Christo Lolov created KAFKA-15427:
-
Summary: Integration tests in TS test harness detect resource leaks
Key: KAFKA-15427
URL: https://issues.apache.org/jira/browse/KAFKA-15427
Project: Kafka
1 - 100 of 155 matches
Mail list logo
