[
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
pache/kafka-site/pull/723
Thanks,
Christo
teers.
Best,
Christo
On Tue, 9 Sept 2025 at 00:18, Matthias J. Sax wrote:
> Hello,
>
> I would like to thank Mickael for being the RM for AK 4.1.0 release!
> Congrats for getting it out!
>
> Given that 4.1 shipped, I would like to kick the tires for AK 4.2 :)
>
>
Thanks for confirming, Matthias!
I am closing this voting thread and I will be creating a new release
candidate later today/tomorrow!
Best,
Christo
On Mon, 8 Sept 2025 at 21:42, Matthias J. Sax wrote:
> Thank you Christo.
>
> We just completed the work to resolve KAFKA-19668.
&g
Heya Matthias,
I have no issue with creating a new RC once the solution is in. The issue
does sound critical enough to be fixed given that the previous method was
removed.
Best,
Christo
On Wed, 3 Sept 2025 at 17:58, Matthias J. Sax wrote:
> Hello,
>
> I hate to be the messenger (ag
all the help!
Best,
Christo
On Wed, 3 Sept 2025 at 15:19, Hong-Yi Chen wrote:
> Hi Christo,
>
> I verified 4.0.1-rc1 as follows:
>
> - Built and ran all unit and integration tests from the source tarball
> (OpenJDK 23 Zulu)
> - Verified basic produce and consume funct
more pass to see what could have caused
what you linked to not be included.
Thanks once again!
Best,
Christo
On Thu, 28 Aug 2025 at 14:23, Lianet M. wrote:
> Hi Christo,
>
> Other than the missing Docker artifacts (kafka and kafka-native), I also
> noticed that some KS Jiras (recen
* Tested enabling, producing, consuming and disabling of queues
* Spot checked the Javadocs
+1 (non-binding)
Best,
Christo
On Wed, 20 Aug 2025 at 18:23, Federico Valeri wrote:
> Hello Mickael,
>
> I did the following:
>
> - Build from source using JDK 17
> - Ran all unit and integra
Build Test Pipeline (JVM):
https://github.com/apache/kafka/actions/runs/17068524479
Docker Build Test Pipeline (Native):
https://github.com/apache/kafka/actions/runs/17068533707
Thanks,
Christo
Hello!
I am closing the vote for this release candidate and will aim to create a
new release candidate following the above two discussions later
today/tomorrow. Thank you for looking into it!
Best,
Christo
On Mon, 4 Aug 2025 at 03:30, Luke Chen wrote:
> Hi Christo,
>
> Could you ta
://cwiki.apache.org/confluence/display/KAFKA/Queues+for+Kafka+%28KIP-932%29+-+Preview+Release+Notes
and I am able to produce and consume using the CLI tools without it?
I don't feel that my documentation-related queries are a blocker. As
such +1 (binding) for this release candidate from me :)
Best,
Christo
kafka/actions/runs/16501196196
Thanks,
Christo
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.
&
to reach out with any questions or
concerns about the schedule!
Best,
Christo
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 testi
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, Iv
r proposal you put multiple
partitions in the same blob. What and how will move this data back to the
old format used by TS?
How will you handle compaction?
How will you handle indexes?
How will you handle transactions?
Once again, this is quite exciting, so thanks for the contribution!
Best,
Chris
compile + runtime broker-only dependencies is currently 16
(if I have done my analysis correctly). What problem(s) do you envision
w.r.t. spilling to disk which we wouldn't be able to solve with our own
implementation that require SQLite?
Once again, great work so far!
Best,
Christo
On Sun, 20 Apr
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
stage in the merge queue + this PR? Or
am I misunderstanding the sequence of events?
Best,
Christo
On Fri, 24 Jan 2025 at 04:20, Chris Egerton wrote:
> Hi David,
>
> Thanks for the KIP, and for your ongoing work to improve Kafka CI.
>
> Two small thoughts:
>
> 1) Today, there
[
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 everyo
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
(TopicIdPartition topicIdPartition,
int epochForOffset, long offset) throws RemoteStorageException
This will help plugin implementers to build optimisations such as skip
lists which will give them the next segment quicker than a linear search.
I am keen to hear your thoughts!
Best,
Christo
On Fri, 4 Oct
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
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 Th
e way to achieve this is to keep the
remote.log.disable.policy, but only allow it to take a value of "delete".
What are your thoughts?
Best,
Christo
On Thu, 25 Jul 2024 at 12:10, Luke Chen wrote:
> Hi all,
>
> I just found the table is not able to be displayed correctly i
Hello!
Makes sense thank you for pointing it out, I will aim to update the
section. I also need to add to the section for metrics!
Best,
Christo
On Mon, 15 Jul 2024 at 19:45, Jun Rao wrote:
> Hi, Christo,
>
> Thanks for the KIP and sorry for the late reply.
>
> Since this
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
f the
community decides that they do in fact want one more 3.x release.
I will mark the KRaft part as ready to be started and aiming for either 4.0
or 3.9.
Best,
Christo
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
8.
Best,
Christo
On Fri, 10 May 2024 at 11:11, Luke Chen wrote:
> Hi Christo,
>
> > 1. I am not certain I follow the question. From DISABLED you can only go
> to
> ENABLED regardless of whether your cluster is backed by Zookeeper or KRaft.
> Am I misunderstanding your
implementation) happen synchronously. Should people
run into timeout problems we can always then have a follow-up KIP where we
make it asynchronous.
Best,
Christo
On Tue, 7 May 2024 at 10:04, Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Hi Christo,
>
> Thanks for the
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,
> >
>
)) and one at what you are proposing? As an
operator I would find it strange to not see the metric in the
RequestMetrics.
Your thoughts?
Best,
Christo
On Sun, 28 Apr 2024 at 10:52, Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Christo,
>
> Updated the KIP with t
twork/RequestChannel.scala#L521-L527
and https://kafka.apache.org/documentation/#tiered_storage_monitoring.
If I am right, then I believe it would be very useful if this KIP also
introduces such a metric because the two are tightly coupled.
What do you think?
Best,
Christo
On Sat, 27 Apr 2024 at 11:33, Fed
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.
>
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.
>
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:
>
>
a few changes have been discussed so I will aim to put
them on paper in the upcoming days and let everyone know!
Best,
Christo
On Tue, 9 Apr 2024 at 14:49, Doğuşcan Namal
wrote:
> +1 let's not introduce a new api and mark it immediately as deprecated :)
>
> On your second comment Luke, o
should also trust them to be able to abort
a hanging transaction.
I would support this KIP if it is put to the vote unless there are other
suggestions for improvements!
Best,
Christo
On Thu, 11 Apr 2024 at 16:48, Nikhil Ramakrishnan <
ramakrishnan.nik...@gmail.com> wrote:
> Hi everyo
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!
> >
n the StopReplicas API which will then disappear in KRaft world as it
is already scheduled for deprecation. What do you think?
Best,
Christo
On Wed, 3 Apr 2024 at 07:59, Luke Chen wrote:
> Hi Christo,
>
> 1. I agree with Doguscan that in KRaft mode, the controller won't send RPCs
>
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
if you introduce a new offset
(i.e. pending-upload-offset) you have to make a change to the ListOffsets
API (i.e. introduce -6) and thus document it in this KIP as such. However,
the last-tiered-offset ought to already be exposed as part of KIP-1005
(under implementation). Am I misunderstanding someth
it just won't have an effect. Granted, I do believe we
should restrict the policy being changed while a disablement is ongoing.
re: Satish and Kamal
104, 1 and 2 are fair asks, I will work with Doguscan to update the KIP
with the information!
Best,
Christo
On Thu, 28 Mar 2024 at 10:31, Doğuş
- earliest-pending-upload-offset or the
latest-tiered-offset? If it is the second, then I believe KIP-1005 ought to
already be exposing that offset as part of the ListOffsets API, no?
Best,
Christo
On Wed, 27 Mar 2024 at 18:23, Abhijeet Kumar
wrote:
> Hi All,
>
> I have created KIP-1023 to
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
?
Best,
Christo
On Thu, 14 Mar 2024 at 06:12, Luke Chen wrote:
> Hi Christo,
>
> Any update with this KIP?
> If you don't have time to complete it, I can collaborate with you to work
> on it.
>
> Thanks.
> Luke
>
> On Wed, Jan 17, 2024 at 11:38 PM Satish
welcome!
Best,
Christo
On Tue, 9 Jan 2024 at 09:44, Doğuşcan Namal
wrote:
> Hi everyone, any progress on the status of this KIP? Overall looks good to
> me but I wonder whether we still need to support it for Zookeeper mode
> given that it will be deprecated in the next 3 months.
>
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
Thank you everyone for casting your votes!
KIP-1005 passes with 6 +1 (three binding and three not binding) - I will
get down to implementing it :)
Best,
Christo
On Tue, 16 Jan 2024 at 01:35, Luke Chen wrote:
> +1 binding from me.
>
> Thanks for the KIP!
> Luke
>
> On Fri,
[
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
Heya!
Okay, your suggestion also makes sense to me!
I have updated the KIP.
Best,
Christo
On Mon, 15 Jan 2024 at 11:51, Luke Chen wrote:
> Hi Christo,
>
> Thanks for the update.
> For "-4 or earliest-local" but tiered storage disabled, I agree it should
> work as
. Let me
know if you disagree!
Best,
Christo
On Fri, 12 Jan 2024 at 03:43, Luke Chen wrote:
> Hi Christo,
>
> Thanks for the KIP!
> One question:
>
> What will the offset return if tiered storage is disabled?
> For "-4 or earliest-local", it should be the same as &
Thank you Divij!
I have updated the KIP to explicitly state that the broker will have a
different behaviour when a timestamp of -5 is requested as part of
ListOffsets.
Best,
Christo
On Tue, 2 Jan 2024 at 11:10, Divij Vaidya wrote:
> Thanks for the KIP Christo.
>
> The shell command
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,
>
&g
Christo Lolov created KAFKA-16002:
-
Summary: Implement RemoteCopyLagSegments, RemoteDeleteLagBytes and
RemoteDeleteLagSegments
Key: KAFKA-16002
URL: https://issues.apache.org/jira/browse/KAFKA-16002
Hello all,
With 3 +1 binding and 1 +1 non-binding votes KIP-963 is adopted 🥳!
I will get down to implementing it.
Best,
Christo
On Tue, 21 Nov 2023 at 07:22, Luke Chen wrote:
> +1 (binding) from me.
> Thanks for the KIP.
>
> Luke
>
> On Tue, Nov 21, 2023 at 11:53 AM Satis
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
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
needs more explanations regarding the changes needed to the OffsetSpec or
others.
Best,
Christo
On Tue, 21 Nov 2023 at 04:20, Satish Duggana
changing the AdminClient and in particular the GetOffsetShell tool.
I am looking forward to your suggestions for improvement!
Best,
Christo
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
, hence we will be
serving requests for those from remote. Am I wrong?
Best,
Christo
On Thu, 16 Nov 2023 at 08:45, Satish Duggana
wrote:
> Thanks Christo for your reply.
>
> 101 and 102 We have conclusion on them.
>
> 103. I am not strongly opinionated on this. I am fine if
will aim to include it.
*re: Kamal*
1. I can add this to the KIP, but similar to what I have mentioned earlier,
I believe these are better left to plugin implementations, no?
2. Yeah, this makes sense.
Best,
Christo
On Fri, 10 Nov 2023 at 09:33, Satish Duggana
wrote:
> Thanks Christo for
ri, 27 Oct 2023 at 15:24, Jorge Esteban Quilcate Otoya <
quilcate.jo...@gmail.com> wrote:
> Hi Christo,
>
> Thanks for proposing KIP, this metrics will certainly be useful to operate
> Kafka Tiered Storage as it becomes production-ready.
>
> 1. Given that the scope of the KI
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
back to you.
Best,
Christo
On Mon, 25 Sept 2023 at 10:49, Gantigmaa Selenge
wrote:
> Hi Christo,
>
> Thank you for writing the KIP.
>
> I recently raised a PR to add metrics for tracking remote segment deletions
> (https://github.com/apache/kafka/pull/14375) but realised th
[
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
title in the KIPs page, that's my miss
Best,
Christo
On Tue, 19 Sept 2023 at 13:21, Divij Vaidya wrote:
> Hey Satish
>
> Thank you for managing this release. I have a few comments:
>
> Documentation
>
> 1. Section: Zookeeper/Stable Version - The documentation states &q
[
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
[
https://issues.apache.org/jira/browse/KAFKA-15298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christo Lolov resolved KAFKA-15298.
---
Resolution: Won't Fix
> Disable DeleteRecords on Tiered Storag
with whether I need to change
*remote.log.manager.task.interval.ms
<http://remote.log.manager.task.interval.ms> *to a lower or higher value.
What are your thoughts on the above? Would you find some of them more
useful than others?
Best,
Christo
On Tue, 8 Aug 2023 at 16:43, Kamal Chandrap
1 - 100 of 163 matches
Mail list logo
