Re: [DISCUSS] KIP-1130: Add metrics indicating the connection count exceeds

[Chia-Ping Tsai]

hi Teng

Thanks for this KIP. Some questions are listed below.

chia_0:

The listener is included by the tag, so should it be removed from “name”. 

${listener_name}-waiting-connection -> waiting-connection

Best,
Chia-Ping




> TengYao Chi  於 2025年4月13日 下午2:50 寫道：
> 
> Hello everyone,
> 
> I want to start a discussion thread on KIP-1130
> , which proposes adding
> metrics indicating the connection count exceeds
> 
> Please take a look and let me know what you think.
> I would appreciate any suggestions and feedback.
> 
> Best regards,
> TengYao

[jira] [Created] (KAFKA-19135) Add IQ Support - move from feature branch

[Bill Bejeck (Jira)]

Bill Bejeck created KAFKA-19135:
---

 Summary: Add IQ Support - move from feature branch
 Key: KAFKA-19135
 URL: https://issues.apache.org/jira/browse/KAFKA-19135
 Project: Kafka
  Issue Type: Task
  Components: streams
Reporter: Bill Bejeck
Assignee: Bill Bejeck
 Fix For: 4.1.0


This initial ticket for IQ support is for moving IQ support from feature branch 
to trunk



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] KIP-1130: Add metrics indicating the connection count exceeds

[TengYao Chi]

Hi Chia-Ping

chia_0: Thanks for pointing that out. I have fixed it.

Best Regards,
TengYao

Chia-Ping Tsai  於 2025年4月13日 週日 下午3:42寫道：

> hi Teng
>
> Thanks for this KIP. Some questions are listed below.
>
> chia_0:
>
> The listener is included by the tag, so should it be removed from “name”.
>
> ${listener_name}-waiting-connection -> waiting-connection
>
> Best,
> Chia-Ping
>
>
>
>
> > TengYao Chi  於 2025年4月13日 下午2:50 寫道：
> >
> > Hello everyone,
> >
> > I want to start a discussion thread on KIP-1130
> > , which proposes adding
> > metrics indicating the connection count exceeds
> >
> > Please take a look and let me know what you think.
> > I would appreciate any suggestions and feedback.
> >
> > Best regards,
> > TengYao
>

Re: [VOTE] KIP-1133: AK Documentation and Website in Markdown

[Harish Vishwanath]

Hi all, thanks for the votes.

We have 5 binding (Andrew Schofield, Matthias J. Sax, Bruno Cadonna, David
Arthur and Chia-Ping Tsai) and 5 non-binding (TengYao Chi, PoAn Yang, Kuon
Po Tseng, Taiju Wu and Jiunn-Yang) votes.

I will now close the voting and mark KIP 1133 as accepted.

Regards,
Harish


On Thu, Apr 3, 2025 at 8:42 PM 黃竣陽  wrote:

> Thanks for this KIP,
>
> +1 (non-binding)
>
> Best Regards,
> Jiunn-Yang
>
> > Kirk True  於 2025年4月4日 凌晨1:21 寫道：
> >
> > +1 (non-binding)
> >
> > On Thu, Apr 3, 2025, at 6:43 AM, TaiJu Wu wrote:
> >> Thanks for this KIP,
> >>
> >> +1(non-binding)
> >>
> >> Best,
> >> TaiJuWu
> >>
> >> On Thu, Apr 3, 2025 at 9:42 PM Kuan Po Tseng 
> wrote:
> >>
> >>> Hi Harish,
> >>>
> >>> Thank you for improving the documentation!
> >>>
> >>> +1 (non-binding)
> >>>
> >>> Best,
> >>> Kuan-Po Tseng
> >>>
> >>> On 2025/03/27 09:30:12 Andrew Schofield wrote:
>  Hi Harish,
>  Thanks for this great KIP. I’m really looking forward to being able to
> >>> write Kafka docs in Markdown instead of HTML.
> 
>  +1 (binding)
> 
>  Thanks,
>  Andrew
> 
>  From: Harish Vishwanath 
>  Date: Wednesday, 26 March 2025 at 23:38
>  To: dev@kafka.apache.org 
>  Subject: [VOTE] KIP-1133: AK Documentation and Website in Markdown
>  Hey all
> 
>  I would like to call a vote on KIP-1133: AK Documentation and Website
> in
>  Markdown.
> 
>  KIP:
> 
> >>>
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FKAFKA%2FKIP-1133%253A%2BAK%2BDocumentation%2Band%2BWebsite%2Bin%2BMarkdown&data=05%7C02%7C%7C940186c5945340391d7a08dd6cbf46dc%7C84df9e7fe9f640afb435%7C1%7C0%7C638786290955636991%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=YK70nZlRbBzQ6nRuYaGJdD4Au8oFKONv6d8EL%2BpuTu4%3D&reserved=0
> >>> <
> >>>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1133%3A+AK+Documentation+and+Website+in+Markdown
> 
> 
>  Discussion thread:
> 
> >>>
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fkc0kg0dxy6xdrwyv10k56k6g058ng2dw&data=05%7C02%7C%7C940186c5945340391d7a08dd6cbf46dc%7C84df9e7fe9f640afb435%7C1%7C0%7C638786290955681824%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2FtrIYkj5dW48vAn4V2RkYHZcJulIsnBxRcfeM8avDYI%3D&reserved=0
> >>> 
> 
>  Regards
>  Harish
> 
> >>>
>
>

[jira] [Resolved] (KAFKA-15371) MetadataShell is stuck when bootstrapping

[Chia-Ping Tsai (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chia-Ping Tsai resolved KAFKA-15371.

Fix Version/s: 4.1.0
   Resolution: Fixed

> MetadataShell is stuck when bootstrapping
> -
>
> Key: KAFKA-15371
> URL: https://issues.apache.org/jira/browse/KAFKA-15371
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 3.5.1
>Reporter: Deng Ziming
>Assignee: xuanzhang gong
>Priority: Major
> Fix For: 4.1.0
>
> Attachments: image-2023-08-17-10-35-01-039.png, 
> image-2023-08-17-10-35-36-067.png, image-2023-10-31-09-04-53-966.png, 
> image-2023-10-31-09-11-53-118.png, image-2023-10-31-09-12-19-051.png, 
> image-2023-10-31-09-15-34-821.png
>
>
> I  downloaded the 3.5.1 package and startup it, then use metadata shell to 
> inspect the data
>  
> {code:java}
> // shell
> bin/kafka-metadata-shell.sh --snapshot 
> /tmp/kraft-combined-logs/__cluster_metadata-0/.log  {code}
> Then process will stuck at loading.
>  
>  
> !image-2023-08-17-10-35-36-067.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-19136) Merge MetadataLogConfig into KRaftConfigs

[Chia-Ping Tsai (Jira)]

Chia-Ping Tsai created KAFKA-19136:
--

 Summary: Merge MetadataLogConfig into KRaftConfigs
 Key: KAFKA-19136
 URL: https://issues.apache.org/jira/browse/KAFKA-19136
 Project: Kafka
  Issue Type: Improvement
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai


Most config class consists of definition and POJO, so we should merge 
MetadataLogConfig with KRaftConfigs



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

RE: Re: [DISCUSS] KIP-1117 Support keystore with multiple alias entries

[Rahul Nirgude]

Hi Mickel,



I have updated the PR and KIP as per below review comment.

Could you please verify this now?


Rahul Nirgude
Lead Software Engineer

Mastercard
Bluegrass Business Park
tel - | mobile 8793830455
[cid:image001.png@01DBAD21.D28529F0]


From: Mickael Maison 
Sent: 19 March 2025 21:47
To: dev 
Subject: {EXTERNAL} Re: [DISCUSS] KIP-1117 Support keystore with multiple alias 
entries

Hi, Thanks for the KIP, overall it seems like a useful improvement. A few 
suggestions mostly on the form: MM1: The current documentation string seems to 
indicate this is only used by clients. SslConfigs are used by both clients and 
servers. 


Hi,



Thanks for the KIP, overall it seems like a useful improvement.



A few suggestions mostly on the form:

MM1: The current documentation string seems to indicate this is only used

by clients. SslConfigs are used by both clients and servers. So I think the

docstring should be rephrased as I expect this to be usable by both sides.

Also the first sentence has an issue/typo "This is config is used".



MM2: We actual code of the "applyAliasToKM()" method is not important in

the KIP. The main goals of a KIP are to describe the motivation, the actual

changes to the public APIs and the compatibility implications for users.

The code will be discussed in the pull request. For example instead of

having the code, I'd rather have a description of what happens if you

provide an alias that does not exist, the error conditions are part of the

changes.



MM3: In the "Test Plan" section you need to describe the testing you plan

to have in the Apache Kafka code base when adding the feature. All changes

need to be covered by tests. Considering the small scope of the proposal,

you can probably just say something like "This will be tested using unit

and integration tests" but it's important to understand you'll need to

write some tests. Saying "it works in my environment" is not acceptable.



Thanks,

Mickael



On Tue, Mar 4, 2025 at 2:12 PM Rahul Nirgude

mailto:rahul.nirg...@mastercard.com.invalid>>
 wrote:



> Hi All,

>

>

>

> I would like to start a discussion on our KIP for *Support keystore with

> multiple alias entries*. Please find the below KIP details.

>

> *KIP-1117* :

> https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/KAFKA/KIP-1117*3A*Support*keystore*with*multiple*alias*entries__;JSsrKysrKw!!NDdRaFrjhKsg!p8GO2V7dFeN1CgA0M8Wm_zt2GDBmfeisbHB5M5oYsHmMo88IDwZx-3ML7SYchn4Vgxl3UtyycgFNN9wWpDtO17lrlquJOw$

> .

>

>

>

> Please review it and share your inputs on this.

>

>

>

>

>

>

>

> *Rahul Nirgude*

>

> Senior Software Engineer

>

>

>

> Mastercard

>

> Business Bay | Tower A

>

> tel - | mobile 8793830455

>

>  >

>

>

> CONFIDENTIALITY NOTICE This e-mail message and any attachments are only

> for the use of the intended recipient and may contain information that is

> privileged, confidential or exempt from disclosure under applicable law. If

> you are not the intended recipient, any disclosure, distribution or other

> use of this e-mail message or attachments is prohibited. If you have

> received this e-mail message in error, please delete and notify the sender

> immediately. Thank you.

>

CONFIDENTIALITY NOTICE This e-mail message and any attachments are only for the 
use of the intended recipient and may contain information that is privileged, 
confidential or exempt from disclosure under applicable law. If you are not the 
intended recipient, any disclosure, distribution or other use of this e-mail 
message or attachments is prohibited. If you have received this e-mail message 
in error, please delete and notify the sender immediately. Thank you.

Re: [VOTE] KIP-1148: Remove log.cleaner.enable configuration

[TengYao Chi]

Hello everyone,

The vote is now closed, and the KIP has been accepted with 3 binding +1s
from
Chia-Ping, Andrew, and Lianet

As well as 3 non-binding +1 from
Kuan Po, Jiunn-Yang, and PoAn.

Thank you all for your participation!

Sincerely,
TengYao

Lianet M.  於 2025年4月10日 週四 下午8:48寫道：

> Thanks for the KIP!
>
> +1 (binding)
>
> Lianet
>
> On Thu, Apr 10, 2025 at 7:17 AM PoAn Yang  wrote:
>
> > Thanks for the KIP.
> >
> > +1 (non-binding)
> >
> > PoAn
> >
> > > On Apr 10, 2025, at 6:55 PM, 黃竣陽  wrote:
> > >
> > > Thanks for the KIP.
> > >
> > > +1 (non-binding),
> > >
> > >> Andrew Schofield  於 2025年4月10日
> > 下午4:30 寫道：
> > >>
> > >> Thanks for the KIP.
> > >>
> > >> +1 (binding)
> > >>
> > >> Andrew
> > >>
> > >> From: Kuan Po Tseng 
> > >> Date: Thursday, 10 April 2025 at 09:05
> > >> To: dev@kafka.apache.org 
> > >> Subject: Re: [VOTE] KIP-1148: Remove log.cleaner.enable configuration
> > >>
> > >> +1 (non-binding), thanks for the KIP.
> > >>
> > >> On 2025/04/10 07:51:53 TengYao Chi wrote:
> > >>> Hello everyone,
> > >>>
> > >>> I would like to call a vote on KIP-1148
> > >>> <
> >
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fx%2FXAyWF&data=05%7C02%7C%7Ca95de0e322b14c71981208dd78066a6c%7C84df9e7fe9f640afb435%7C1%7C0%7C638798691134154001%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=mg8M%2BJIBvr0eB4oPlrON32XTS8APRL05LZG%2FPPgXaYc%3D&reserved=0
> > >.
> > >>>
> > >>> Here <
> >
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fdjgd2gzl1n2qlqw48mcxnr8h9sob32yz&data=05%7C02%7C%7Ca95de0e322b14c71981208dd78066a6c%7C84df9e7fe9f640afb435%7C1%7C0%7C638798691134177534%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PMYeZ68%2BFkcSm66KXaYTz0zD4Kyjp4lhE%2FTKekBveDY%3D&reserved=0
> > > is
> > >>> the discussion thread.
> > >>>
> > >>>
> > >>> Best Regards,
> > >>> TengYao
> > >>>
> > >
> >
> >
>

Re: [DISCUSS] KIP-1146: Anchored wall-clock punctuation

[Herman K. Jakobsen]

Thank you for your inputs!

It looks like my previous answer messed up the mailing thread due to the
use of the hashtag symbol when creating the following list. I've tried to
reformat the list:

(1) I agree and I have changed the `startTime` parameter to be of type
`Instant`.

(2) I have added a section for the unintuitive cases and semantics that you
and Sophie have mentioned. In short, I’m proposing to skip forward to the
next trigger time.

(3) It was a typo - the correct term was wall clock time (i.e. system time).

(4-5) My initial proposal of only supporting wall clock time was based on
my restricted knowledge of the Kafka Streams and Punctuations internals. I
did not know if it would be demanding/complex to work with stream time.
Based on your inputs, it seems like it would be just as much work to
gracefully handle the unsupported stream time than it is to actually just
implement support for it. Hence, I’m proposing to implement support for
both wall clock time and stream time in this KIP.

Best regards,
Herman

tor. 3. apr. 2025 kl. 06:57 skrev Sophie Blee-Goldman :

> Thanks for the KIP!
>
> I pretty much echo what Matthias has said so far regarding the API.
>
> Regarding #4-5, assuming we would just be leaving out stream-time in the
> initial implementation for time/scope reasons and might want to add this in
> the future, I think it's best to just throw an exception if this is used
> with STREAM_TIME for now. Especially if it's only a short time before we
> support stream-time, which seems likely unless for some reason it is
> significantly more difficult to implement this for stream-time vs for
> wall-clock time. And I can't imagine that it would be.
>
> As for the actual semantics, perhaps it would be useful to include a brief
> example including how it behaves on startup/after a restart.
>
> Let's say you schedule a punctuation with a start time of 100 and an
> interval of 10 seconds. If you first start up at t=201, my understanding is
> that you'd wait until t=210 to trigger the first punctuation, and after
> that they would proceed as usual in 10s increments?
> So if your app happened to shut down at t=209 and didn't come back up again
> until t=211, you would miss the punctuation at t=210 and would have to wait
> until t=220 to run the punctuator?
>
> That's more or less how the punctuator works now, just want to make sure
> this is clear in the KIP.
>
> In fact, this KIP seems to actually remedy a long-standing issue with
> wall-clock punctuators, which is that they'll never be triggered if the app
> or task is restarted within the punctuation interval. With anchored
> punctuations you can technically still miss the punctuation if it restarts
> exactly when it was scheduled, but that should be fairly rare, so in
> general frequent restarts won't be a problem for punctuations anymore.
> Neat!
>
> On Tue, Apr 1, 2025 at 6:12 PM Matthias J. Sax  wrote:
>
> > Herman,
> >
> > thanks for the KIP, and sorry for late response. Overall the KIP makes
> > sense to me, and the propose API change is neat and contained, so I
> > don't have any concerns about it.
> >
> > Couple of questions/comments.
> >
> > (1) I think the propose `startTime` parameter should not be a `long` but
> > in `Instance` type?
> >
> >
> > (2) What happens is the passed in `startTime` is in the past? Would an
> > exception be thrown? Or just "skip forward" to the next "firing point"
> > in the future?
> >
> >
> > (3) The KIP says
> >
> > > It is planned that only wall clock (i.e. stream time) is supported in
> > this first iteration.
> >
> > This is confusing. Wall-clock time is not the same as stream time. Maybe
> > just a typo.
> >
> >
> > (4) Why are you excluding "stream time"? Also, the KIP does not define
> > what happens if the new overload is used in combination with "stream
> > time" -- I assume the method would throw an exception, what might not be
> > ideal API ergonomics (cf (5) below).
> >
> > (5) If we really want to exclude "stream-time", I am wondering if we
> > could use
> >
> >  Cancellable schedule(final Duration interval, final long startTime,
> > final Punctuator callback)
> >
> > instead, omitting the `PunctuationType` parameter and document clearly
> > in the JavaDocs that wall-clock time punctuation are used. This way,
> > users cannot write incorrect code and don't need to worry about
> exceptions.
> >
> >
> >
> >
> > -Matthias
> >
> >
> > On 3/22/25 1:24 AM, Herman K. Jakobsen wrote:
> > > Hi all,
> > >
> > > I would like to start a discussion thread on
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1146%3A+Anchored+wall-clock+punctuation
> > >
> > > Best regards,
> > > Herman
> > >
> >
> >
>

[jira] [Resolved] (KAFKA-19071) Incorrect documentation for remote.storage.enable

[Luke Chen (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-19071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luke Chen resolved KAFKA-19071.
---
Fix Version/s: 4.1.0
   3.9.1
   4.0.1
   Resolution: Fixed

> Incorrect documentation for remote.storage.enable
> -
>
> Key: KAFKA-19071
> URL: https://issues.apache.org/jira/browse/KAFKA-19071
> Project: Kafka
>  Issue Type: Bug
>Reporter: Azhar Ahmed
>Assignee: Azhar Ahmed
>Priority: Minor
> Fix For: 4.1.0, 3.9.1, 4.0.1
>
>
> As of 3.9, Kafka allows disabling remote storage on a topic after it was 
> enabled. It allows subsequent enabling and disabling too.
> However the documentation says otherwise and needs to be corrected.
> Doc: 
> https://kafka.apache.org/39/documentation/#topicconfigs_remote.storage.enable



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #267

[Apache Jenkins Server]

See 

Re: Requesting permission to contribute to Apache Kafka

[Luke Chen]

Hi Divya,

Your account should be all set.

Thanks.
Luke

On Sat, Apr 12, 2025 at 7:25 PM Divya Guduru 
wrote:

> I have access to the JIRA
> board but cannot assign issues to myself. Could you give contributor
> permissions to Jira ID: divya2890
>
>
> Regards
> Divya
>
>
> On Sat, Apr 12, 2025 at 1:38 PM Divya Guduru 
> wrote:
>
> > Hello,
> >
> > My Jira id is divya2890
> >
> > Could you please grant me the necessary permissions to self-assign JIRA
> > issues?
> >
> > Regards
> > Divya
> >
>