Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread Satish Duggana
Congratulations Tom! On Fri, 19 Nov 2021 at 05:53, John Roesler wrote: > Congratulations, Tom! > > On Thu, Nov 18, 2021, at 17:53, Konstantine Karantasis wrote: > > Congratulations Tom! > > > > Konstantine > > > > > > On Thu, Nov 18, 2021 at 2:44 PM Luke Chen wrote: > > > >> Congrats, Tom! >

[jira] [Created] (KAFKA-13465) when auto create topics enable,server create inner topic of MirrorMaker unexpectedly

2021-11-18 Thread ZhenChun Pan (Jira)
ZhenChun Pan created KAFKA-13465: Summary: when auto create topics enable,server create inner topic of MirrorMaker unexpectedly Key: KAFKA-13465 URL: https://issues.apache.org/jira/browse/KAFKA-13465

Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread John Roesler
Congratulations, Tom! On Thu, Nov 18, 2021, at 17:53, Konstantine Karantasis wrote: > Congratulations Tom! > > Konstantine > > > On Thu, Nov 18, 2021 at 2:44 PM Luke Chen wrote: > >> Congrats, Tom! >> >> Guozhang Wang 於 2021年11月19日 週五 上午1:13 寫道: >> >> > Congrats Tom! >> > >> > Guozhang >> > >>

Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread Konstantine Karantasis
Congratulations Tom! Konstantine On Thu, Nov 18, 2021 at 2:44 PM Luke Chen wrote: > Congrats, Tom! > > Guozhang Wang 於 2021年11月19日 週五 上午1:13 寫道: > > > Congrats Tom! > > > > Guozhang > > > > On Thu, Nov 18, 2021 at 7:49 AM Jun Rao > wrote: > > > > > Hi, Everyone, > > > > > > Tom Bentley has

[jira] [Created] (KAFKA-13464) SCRAM does not validate client-final-message's nonce

2021-11-18 Thread Travis Bischel (Jira)
Travis Bischel created KAFKA-13464: -- Summary: SCRAM does not validate client-final-message's nonce Key: KAFKA-13464 URL: https://issues.apache.org/jira/browse/KAFKA-13464 Project: Kafka

Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread Luke Chen
Congrats, Tom! Guozhang Wang 於 2021年11月19日 週五 上午1:13 寫道: > Congrats Tom! > > Guozhang > > On Thu, Nov 18, 2021 at 7:49 AM Jun Rao wrote: > > > Hi, Everyone, > > > > Tom Bentley has been a Kafka committer since Mar. 15, 2021. He has been > > very instrumental to the community since becoming a

Re: [VOTE} KIP-796: Interactive Query v2

2021-11-18 Thread Patrick Stuedi
+1 (non-binding), thanks John! -Patrick On Thu, Nov 18, 2021 at 12:27 AM John Roesler wrote: > Hello all, > > I'd like to open the vote for KIP-796, which proposes > a revamp of the Interactive Query APIs in Kafka Streams. > > The proposal is here: > https://cwiki.apache.org/confluence/x/34xnCw

Re: [DISCUSS] KIP-778 KRaft Upgrades

2021-11-18 Thread David Arthur
Jun, The KIP has some changes to the CLI for KIP-584. With Jason's suggestion incorporated, these three commands would look like: 1) kafka-features.sh upgrade --release latest upgrades all known features to their defaults in the latest release 2) kafka-features.sh downgrade --release 3.x

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.1 #21

2021-11-18 Thread Apache Jenkins Server
See Changes: -- [...truncated 501600 lines...] [2021-11-18T18:45:09.077Z] > Task :raft:testClasses UP-TO-DATE [2021-11-18T18:45:09.077Z] > Task :connect:json:testJar

Re: Errors thrown from a KStream transformer are swallowed, eg. StackOverflowError

2021-11-18 Thread Sophie Blee-Goldman
Would you mind filing a ticket for this? Would be nice to have it on the books so other users know we know about it, and more importantly which versions this is and is not fixed in. Thanks for the report! On Thu, Nov 18, 2021 at 6:10 AM John Roesler wrote: > Thanks for pointing that out,

Re: [DISCUSS] KIP-778 KRaft Upgrades

2021-11-18 Thread Jun Rao
Hi, Jason, David, Just to clarify on the interaction with the end user, the design in KIP-584 allows one to do the following. (1) kafka-features.sh --upgrade-all --bootstrap-server kafka-broker0.prn1:9071 to upgrade all features to the latest version known by the tool. The user doesn't need to

Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread Guozhang Wang
Congrats Tom! Guozhang On Thu, Nov 18, 2021 at 7:49 AM Jun Rao wrote: > Hi, Everyone, > > Tom Bentley has been a Kafka committer since Mar. 15, 2021. He has been > very instrumental to the community since becoming a committer. It's my > pleasure to announce that Tom is now a member of Kafka

Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread Randall Hauch
Congratulations, Tom! Randall On Thu, Nov 18, 2021 at 10:29 AM Bruno Cadonna wrote: > > Tom, > > Congratulations! > > Best, > Bruno > > On 18.11.21 17:12, David Jacot wrote: > > Congrats, Tom! > > > > On Thu, Nov 18, 2021 at 5:03 PM Mickael Maison > > wrote: > >> > >> Congratulations Tom! >

[GitHub] [kafka-site] mumrah opened a new pull request #384: Update David Arthur photo

2021-11-18 Thread GitBox
mumrah opened a new pull request #384: URL: https://github.com/apache/kafka-site/pull/384 Current photo is about 10 years old, updating to a more recent one (also better quality). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread Bruno Cadonna
Tom, Congratulations! Best, Bruno On 18.11.21 17:12, David Jacot wrote: Congrats, Tom! On Thu, Nov 18, 2021 at 5:03 PM Mickael Maison wrote: Congratulations Tom! On Thu, Nov 18, 2021 at 4:54 PM Chris Egerton wrote: Congrats Tom! On Thu, Nov 18, 2021 at 10:49 AM Jun Rao wrote: Hi,

Re: [DISCUSS] KIP-778 KRaft Upgrades

2021-11-18 Thread David Arthur
Colin, thanks for the detailed response. I understand what you're saying and I agree with your rationale. It seems like we could just initialize their cluster.metadata to 1 when the > software is upgraded to 3.2. > Concretely, this means the controller would see that there is no

Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread David Jacot
Congrats, Tom! On Thu, Nov 18, 2021 at 5:03 PM Mickael Maison wrote: > > Congratulations Tom! > > On Thu, Nov 18, 2021 at 4:54 PM Chris Egerton > wrote: > > > > Congrats Tom! > > > > On Thu, Nov 18, 2021 at 10:49 AM Jun Rao wrote: > > > > > Hi, Everyone, > > > > > > Tom Bentley has been a

Re: [DISCUSS] KIP-714: Client metrics and observability

2021-11-18 Thread Magnus Edenhill
Hi Mickael, see inline. Den ons 10 nov. 2021 kl 15:21 skrev Mickael Maison : > Hi Magnus, > > I see you've addressed some of the points I raised above but some (4, > 5) have not been addressed yet. > Re 4) How will the user/app know metrics are being sent. One possibility is to add a JMX

Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread Mickael Maison
Congratulations Tom! On Thu, Nov 18, 2021 at 4:54 PM Chris Egerton wrote: > > Congrats Tom! > > On Thu, Nov 18, 2021 at 10:49 AM Jun Rao wrote: > > > Hi, Everyone, > > > > Tom Bentley has been a Kafka committer since Mar. 15, 2021. He has been > > very instrumental to the community since

Re: [ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread Chris Egerton
Congrats Tom! On Thu, Nov 18, 2021 at 10:49 AM Jun Rao wrote: > Hi, Everyone, > > Tom Bentley has been a Kafka committer since Mar. 15, 2021. He has been > very instrumental to the community since becoming a committer. It's my > pleasure to announce that Tom is now a member of Kafka PMC. > >

[ANNOUNCE] New Kafka PMC Member: Tom Bentley

2021-11-18 Thread Jun Rao
Hi, Everyone, Tom Bentley has been a Kafka committer since Mar. 15, 2021. He has been very instrumental to the community since becoming a committer. It's my pleasure to announce that Tom is now a member of Kafka PMC. Congratulations Tom! Jun on behalf of Apache Kafka PMC

Re: [DISCUSS] KIP-778 KRaft Upgrades

2021-11-18 Thread David Arthur
Jason, 1/2. You've got it right. The intention is that metadata.version will gate both RPCs (like IBP does) as well as metadata records. So, when a broker sees that metadata.version changed, it may start advertising new RPCs and it will need to refresh the ApiVersions it has for other brokers. I

[jira] [Resolved] (KAFKA-13462) KRaft server does not return internal topics on list topics RPC

2021-11-18 Thread dengziming (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-13462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dengziming resolved KAFKA-13462. Resolution: Invalid __consumer_offsets will not be created unless we store commit offset > KRaft

Re: [VOTE] KIP-784: Add top-level error code field to DescribeLogDirsResponse

2021-11-18 Thread Mickael Maison
Bumping this thread. Let me know if you have any feedback. Thanks, Mickael On Wed, Oct 27, 2021 at 3:25 PM Luke Chen wrote: > > Hi Mickael, > Thanks for the KIP. > It's good to keep it consistent with others, to have top-level error field. > > + 1 (non-binding) > > Thank you. > Luke > > On

Re: Errors thrown from a KStream transformer are swallowed, eg. StackOverflowError

2021-11-18 Thread John Roesler
Thanks for pointing that out, Scott! You’re totally right; that should be a Throwable. Just to put it out there, do you want to just send a quick PR? If not, no worries. I’m just asking because it seems like you’ve already done the hard part and it might be nice to get the contribution credit.

Re: Track topic deletion state without ZK

2021-11-18 Thread Omnia Ibrahim
Hi, To clarify here, what I meant by "stuck" for deletion is regarding the state of LogDir deletion. When the cluster receives a topic deletion request, the KRAFT will delete the topic's metadata and eventually delete all LogDirs on any broker/disk at some point (correct me if I am wrong). My

Errors thrown from a KStream transformer are swallowed, eg. StackOverflowError

2021-11-18 Thread Sinclair Scott
Hi there, I'm a big fan of KStreams - thanks for all the great work!! I unfortunately (my fault) had a StackOverflowError bug in my KStream transformer which meant that the KStream died without reporting any Exception at all. The first log message showed some polling activity and then you

Re: [DISCUSS] KIP-792: Add "generation" field into consumer protocol

2021-11-18 Thread Luke Chen
Hi David, Thanks for your feedback. I've updated the KIP for your comments (1)(2). For (3), it's a good point! Yes, we didn't deserialize the subscription metadata on broker side, and it's not necessary to add overhead on broker side. And, yes, I think we can fix the original issue by adding a

Re: [DISCUSS] KIP-797 Accept duplicate listener on port for IPv4/IPv6

2021-11-18 Thread Matthew de Detrich
Hi Luke, Thanks for the response, I have removed the PR link in the KIP (it was already in the JIRA issue) and I have also updated the code that generates the documentation for https://kafka.apache.org/documentation/#brokerconfigs_listeners (I also added an example of an IPv4+IPv6 listener

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.1 #20

2021-11-18 Thread Apache Jenkins Server
See Changes: -- [...truncated 501458 lines...] [2021-11-18T12:17:51.142Z] [2021-11-18T12:17:51.142Z] You can use '--warning-mode all' to show the individual deprecation

[DISCUSS] KafkaClient parameter optimization: java.security.auth.login.config

2021-11-18 Thread Riven Sun
Hi Kafka devs, I found that when KafkaClient establishes a sasl connection, if `java.security.auth.login.config` is used and multiple LoginModules are configured in JaasConfigFile (regardless of whether these LoginModules are of the same type), KafkaClient will get the wrong username from

Re: [DISCUSS] KIP-797 Accept duplicate listener on port for IPv4/IPv6

2021-11-18 Thread Luke Chen
Hi Matthew, Thanks for the update. The "listener" config description should also be updated: https://kafka.apache.org/documentation/#brokerconfigs_listeners We stated: Listener names and port numbers must be unique. It'll be wrong after this KIP. Also, the PR link should not be put onto the KIP.

Re: [DISCUSS] KIP-797 Accept duplicate listener on port for IPv4/IPv6

2021-11-18 Thread Matthew de Detrich
Hi Luke, I have updated the KIP to make it clear that we are only talking about listeners and not advertised listeners. I have also updated/rebased the PR at https://github.com/apache/kafka/pull/11478 to add upgrade notes about the suggested change. I am not sure if there is an additional place

[DISCUSS] Broker parameter optimization: security.inter.broker.protocol

2021-11-18 Thread Riven Sun
Hi Kafka devs, The default behavior of security.inter.broker.protocol is: "InterBrokerListenerName=ListenerName.forSecurityProtocol(securityProtocol)" . We are not aware of this behavior from the security.inter.broker.protocol comment on the latest official website of Kafka. After using this