Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #16

[Apache Jenkins Server]

See 

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #15

[Apache Jenkins Server]

See 

[jira] [Resolved] (KAFKA-12624) Fix LICENSE in 2.6

[A. Sophie Blee-Goldman (Jira)]

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

A. Sophie Blee-Goldman resolved KAFKA-12624.

Resolution: Fixed

> Fix LICENSE in 2.6
> --
>
> Key: KAFKA-12624
> URL: https://issues.apache.org/jira/browse/KAFKA-12624
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: John Roesler
>Assignee: A. Sophie Blee-Goldman
>Priority: Blocker
> Fix For: 2.6.2
>
>
> Just splitting this out as a sub-task.
> I've fixed the parent ticket on trunk and 2.8.
> You'll need to cherry-pick the fix from 2.8 (see 
> [https://github.com/apache/kafka/pull/10474)]
> Then, you can follow the manual verification steps I detailed here: 
> https://issues.apache.org/jira/browse/KAFKA-12622



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [ANNOUNCE] New Committer: Bruno Cadonna

[Sophie Blee-Goldman]

Congrats!

On Wed, Apr 7, 2021 at 6:32 PM Luke Chen  wrote:

> Congrats Bruno!!
>
> Luke
>
> On Thu, Apr 8, 2021 at 9:18 AM Matthias J. Sax  wrote:
>
> > Congrats Bruno! Very well deserved!
> >
> >
> > -Matthias
> >
> > On 4/7/21 3:51 PM, Bill Bejeck wrote:
> > > Congrats Bruno! Well deserved.
> > >
> > > Bill
> > >
> > > On Wed, Apr 7, 2021 at 6:34 PM Guozhang Wang 
> wrote:
> > >
> > >> Hello all,
> > >>
> > >> I'm happy to announce that Bruno Cadonna has accepted his invitation
> to
> > >> become an Apache Kafka committer.
> > >>
> > >> Bruno has been contributing to Kafka since Jan. 2019 and has made 99
> > >> commits and more than 80 PR reviews so far:
> > >>
> > >> https://github.com/apache/kafka/commits?author=cadonna
> > >>
> > >> He worked on a few key KIPs on Kafka Streams:
> > >>
> > >> * KIP-471: Expose RocksDB Metrics in Kafka Streams
> > >> * KIP-607: Add Metrics to Kafka Streams to Report Properties of
> RocksDB
> > >> * KIP-662: Throw Exception when Source Topics of a Streams App are
> > Deleted
> > >>
> > >> Besides all the code contributions and reviews, he's also done a
> handful
> > >> for the community: multiple Kafka meetup talks in Berlin and Kafka
> > Summit
> > >> talks, an introductory class to Kafka at Humboldt-Universität zu
> Berlin
> > >> seminars, and have co-authored a paper on Kafka's stream processing
> > >> semantics in this year's SIGMOD conference (
> > >> https://en.wikipedia.org/wiki/SIGMOD). Bruno has also been quite
> > active on
> > >> SO channels and AK mailings.
> > >>
> > >> Please join me to congratulate Bruno for all the contributions!
> > >>
> > >> -- Guozhang
> > >>
> > >
> >
>

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #14

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 411258 lines...]
[2021-04-07T20:29:13.987Z] 
[2021-04-07T20:29:13.987Z] ControllerIntegrationTest > 
testBackToBackPreferredReplicaLeaderElections() PASSED
[2021-04-07T20:29:13.987Z] 
[2021-04-07T20:29:13.987Z] ControllerIntegrationTest > 
testTopicIdPersistsThroughControllerReelection() STARTED
[2021-04-07T20:29:19.205Z] 
[2021-04-07T20:29:19.205Z] ControllerIntegrationTest > 
testTopicIdPersistsThroughControllerReelection() PASSED
[2021-04-07T20:29:19.205Z] 
[2021-04-07T20:29:19.205Z] ControllerIntegrationTest > 
testControllerFeatureZNodeSetupWhenFeatureVersioningIsDisabledWithNonExistingFeatureZNode()
 STARTED
[2021-04-07T20:29:21.325Z] 
[2021-04-07T20:29:21.325Z] ControllerIntegrationTest > 
testControllerFeatureZNodeSetupWhenFeatureVersioningIsDisabledWithNonExistingFeatureZNode()
 PASSED
[2021-04-07T20:29:21.325Z] 
[2021-04-07T20:29:21.325Z] ControllerIntegrationTest > testEmptyCluster() 
STARTED
[2021-04-07T20:29:24.162Z] 
[2021-04-07T20:29:24.162Z] ControllerIntegrationTest > testEmptyCluster() PASSED
[2021-04-07T20:29:24.162Z] 
[2021-04-07T20:29:24.162Z] ControllerIntegrationTest > 
testControllerMoveOnPreferredReplicaElection() STARTED
[2021-04-07T20:29:27.073Z] 
[2021-04-07T20:29:27.073Z] ControllerIntegrationTest > 
testControllerMoveOnPreferredReplicaElection() PASSED
[2021-04-07T20:29:27.073Z] 
[2021-04-07T20:29:27.073Z] ControllerIntegrationTest > 
testPreferredReplicaLeaderElection() STARTED
[2021-04-07T20:29:33.349Z] 
[2021-04-07T20:29:33.349Z] ControllerIntegrationTest > 
testPreferredReplicaLeaderElection() PASSED
[2021-04-07T20:29:33.349Z] 
[2021-04-07T20:29:33.349Z] ControllerIntegrationTest > 
testMetadataPropagationOnBrokerChange() STARTED
[2021-04-07T20:29:38.765Z] 
[2021-04-07T20:29:38.765Z] ControllerIntegrationTest > 
testMetadataPropagationOnBrokerChange() PASSED
[2021-04-07T20:29:38.765Z] 
[2021-04-07T20:29:38.765Z] ControllerIntegrationTest > 
testControllerFeatureZNodeSetupWhenFeatureVersioningIsEnabledWithDisabledExistingFeatureZNode()
 STARTED
[2021-04-07T20:29:40.927Z] 
[2021-04-07T20:29:40.927Z] ControllerIntegrationTest > 
testControllerFeatureZNodeSetupWhenFeatureVersioningIsEnabledWithDisabledExistingFeatureZNode()
 PASSED
[2021-04-07T20:29:40.927Z] 
[2021-04-07T20:29:40.927Z] ControllerIntegrationTest > 
testMetadataPropagationForOfflineReplicas() STARTED
[2021-04-07T20:29:50.492Z] 
[2021-04-07T20:29:50.492Z] ControllerIntegrationTest > 
testMetadataPropagationForOfflineReplicas() PASSED
[2021-04-07T20:29:50.492Z] 
[2021-04-07T20:29:50.492Z] ControllerIntegrationTest > 
testTopicIdCreatedOnUpgrade() STARTED
[2021-04-07T20:29:54.407Z] 
[2021-04-07T20:29:54.407Z] ControllerIntegrationTest > 
testTopicIdCreatedOnUpgrade() PASSED
[2021-04-07T20:29:54.407Z] 
[2021-04-07T20:29:54.407Z] ControllerIntegrationTest > 
testTopicIdMigrationAndHandling() STARTED
[2021-04-07T20:29:57.896Z] 
[2021-04-07T20:29:57.896Z] ControllerIntegrationTest > 
testTopicIdMigrationAndHandling() PASSED
[2021-04-07T20:29:57.896Z] 
[2021-04-07T20:29:57.896Z] MetricsTest > testUpdateJMXFilter() STARTED
[2021-04-07T20:30:00.885Z] 
[2021-04-07T20:30:00.885Z] MetricsTest > testUpdateJMXFilter() PASSED
[2021-04-07T20:30:00.885Z] 
[2021-04-07T20:30:00.885Z] MetricsTest > 
testGeneralBrokerTopicMetricsAreGreedilyRegistered() STARTED
[2021-04-07T20:30:09.217Z] 
[2021-04-07T20:30:09.217Z] MetricsTest > 
testGeneralBrokerTopicMetricsAreGreedilyRegistered() PASSED
[2021-04-07T20:30:09.217Z] 
[2021-04-07T20:30:09.217Z] MetricsTest > testLinuxIoMetrics() STARTED
[2021-04-07T20:30:10.607Z] 
[2021-04-07T20:30:10.607Z] MetricsTest > testLinuxIoMetrics() PASSED
[2021-04-07T20:30:10.607Z] 
[2021-04-07T20:30:10.607Z] MetricsTest > 
testMetricsReporterAfterDeletingTopic() STARTED
[2021-04-07T20:30:12.874Z] 
[2021-04-07T20:30:12.874Z] MetricsTest > 
testMetricsReporterAfterDeletingTopic() PASSED
[2021-04-07T20:30:12.874Z] 
[2021-04-07T20:30:12.874Z] MetricsTest > testSessionExpireListenerMetrics() 
STARTED
[2021-04-07T20:30:15.233Z] 
[2021-04-07T20:30:15.233Z] MetricsTest > testSessionExpireListenerMetrics() 
PASSED
[2021-04-07T20:30:15.233Z] 
[2021-04-07T20:30:15.233Z] MetricsTest > 
testBrokerTopicMetricsUnregisteredAfterDeletingTopic() STARTED
[2021-04-07T20:30:19.677Z] 
[2021-04-07T20:30:19.677Z] MetricsTest > 
testBrokerTopicMetricsUnregisteredAfterDeletingTopic() PASSED
[2021-04-07T20:30:19.677Z] 
[2021-04-07T20:30:19.677Z] MetricsTest > testYammerMetricsCountMetric() STARTED
[2021-04-07T20:30:21.773Z] 
[2021-04-07T20:30:21.773Z] MetricsTest > testYammerMetricsCountMetric() PASSED
[2021-04-07T20:30:21.773Z] 
[2021-04-07T20:30:21.773Z] MetricsTest > testClusterIdMetric() STARTED
[2021-04-07T20:30:23.913Z] 
[2021-04-07T20:30:23.913Z] MetricsTest > testClusterIdMetric() PASSED
[2021-04-07T20:30:23.913Z] 
[2021-04-07T20:30:23.913Z] MetricsTest > testControllerMetric

Re: [ANNOUNCE] New Committer: Bruno Cadonna

[Luke Chen]

Congrats Bruno!!

Luke

On Thu, Apr 8, 2021 at 9:18 AM Matthias J. Sax  wrote:

> Congrats Bruno! Very well deserved!
>
>
> -Matthias
>
> On 4/7/21 3:51 PM, Bill Bejeck wrote:
> > Congrats Bruno! Well deserved.
> >
> > Bill
> >
> > On Wed, Apr 7, 2021 at 6:34 PM Guozhang Wang  wrote:
> >
> >> Hello all,
> >>
> >> I'm happy to announce that Bruno Cadonna has accepted his invitation to
> >> become an Apache Kafka committer.
> >>
> >> Bruno has been contributing to Kafka since Jan. 2019 and has made 99
> >> commits and more than 80 PR reviews so far:
> >>
> >> https://github.com/apache/kafka/commits?author=cadonna
> >>
> >> He worked on a few key KIPs on Kafka Streams:
> >>
> >> * KIP-471: Expose RocksDB Metrics in Kafka Streams
> >> * KIP-607: Add Metrics to Kafka Streams to Report Properties of RocksDB
> >> * KIP-662: Throw Exception when Source Topics of a Streams App are
> Deleted
> >>
> >> Besides all the code contributions and reviews, he's also done a handful
> >> for the community: multiple Kafka meetup talks in Berlin and Kafka
> Summit
> >> talks, an introductory class to Kafka at Humboldt-Universität zu Berlin
> >> seminars, and have co-authored a paper on Kafka's stream processing
> >> semantics in this year's SIGMOD conference (
> >> https://en.wikipedia.org/wiki/SIGMOD). Bruno has also been quite
> active on
> >> SO channels and AK mailings.
> >>
> >> Please join me to congratulate Bruno for all the contributions!
> >>
> >> -- Guozhang
> >>
> >
>

Re: [ANNOUNCE] New Kafka PMC Member: Bill Bejeck

[Luke Chen]

Congratulations Bill!

Luke

On Thu, Apr 8, 2021 at 9:17 AM Matthias J. Sax  wrote:

> Hi,
>
> It's my pleasure to announce that Bill Bejeck in now a member of the
> Kafka PMC.
>
> Bill has been a Kafka committer since Feb 2019. He has remained
> active in the community since becoming a committer.
>
>
>
> Congratulations Bill!
>
>  -Matthias, on behalf of Apache Kafka PMC
>

Re: [ANNOUNCE] New Committer: Bruno Cadonna

[Matthias J. Sax]

Congrats Bruno! Very well deserved!


-Matthias

On 4/7/21 3:51 PM, Bill Bejeck wrote:
> Congrats Bruno! Well deserved.
> 
> Bill
> 
> On Wed, Apr 7, 2021 at 6:34 PM Guozhang Wang  wrote:
> 
>> Hello all,
>>
>> I'm happy to announce that Bruno Cadonna has accepted his invitation to
>> become an Apache Kafka committer.
>>
>> Bruno has been contributing to Kafka since Jan. 2019 and has made 99
>> commits and more than 80 PR reviews so far:
>>
>> https://github.com/apache/kafka/commits?author=cadonna
>>
>> He worked on a few key KIPs on Kafka Streams:
>>
>> * KIP-471: Expose RocksDB Metrics in Kafka Streams
>> * KIP-607: Add Metrics to Kafka Streams to Report Properties of RocksDB
>> * KIP-662: Throw Exception when Source Topics of a Streams App are Deleted
>>
>> Besides all the code contributions and reviews, he's also done a handful
>> for the community: multiple Kafka meetup talks in Berlin and Kafka Summit
>> talks, an introductory class to Kafka at Humboldt-Universität zu Berlin
>> seminars, and have co-authored a paper on Kafka's stream processing
>> semantics in this year's SIGMOD conference (
>> https://en.wikipedia.org/wiki/SIGMOD). Bruno has also been quite active on
>> SO channels and AK mailings.
>>
>> Please join me to congratulate Bruno for all the contributions!
>>
>> -- Guozhang
>>
> 

[ANNOUNCE] New Kafka PMC Member: Bill Bejeck

[Matthias J. Sax]

Hi,

It's my pleasure to announce that Bill Bejeck in now a member of the
Kafka PMC.

Bill has been a Kafka committer since Feb 2019. He has remained
active in the community since becoming a committer.



Congratulations Bill!

 -Matthias, on behalf of Apache Kafka PMC

Re: [kafka-clients] Subject: [VOTE] 2.8.0 RC1

[Israel Ekpo]

You are very welcome

Thanks for the clarification


On Wed, Apr 7, 2021 at 8:22 PM John Roesler  wrote:

> Ah, thank you for pointing that out, Israel!
>
> Indeed, I neglected to update the date. Yes, let us say
> Tuesday, 13 April 2021 for the testing deadline.
>
> Thanks as well for validating the release!
> -John
>
> On Wed, 2021-04-07 at 16:50 -0400, Israel Ekpo wrote:
> > Hello John,
> >
> > Thanks for running the release for 2.8.0
> >
> > I was reviewing the request for validation for 2.8.0 RC1 it appears that
> > the deadline to complete testing/validation by the community is 6th April
> > 2021
> >
> > Same day delivery :)
> >
> > I think you meant to say Tuesday, April 13 2021 instead.
> >
> > Could we assume that was just a carry over from the previous solicitation
> > for 2.8.0 RC0 and you actually meant to say 2021-04-13?
> >
> > When you have a moment, please clarify.
> >
> > I am running my tests shortly and will share my results by the end of the
> > week.
> >
> > Thanks.
> >
> >
> >
> > On Tue, Apr 6, 2021 at 5:37 PM John Roesler  wrote:
> >
> > > Hello Kafka users, developers and client-developers,
> > >
> > > This is the second candidate for release of Apache Kafka
> > > 2.8.0. This is a major release that includes many new
> > > features, including:
> > >
> > > * Early-access release of replacing Zookeeper with a self-
> > > managed quorum
> > > * Add Describe Cluster API
> > > * Support mutual TLS authentication on SASL_SSL listeners
> > > * Ergonomic improvements to Streams TopologyTestDriver
> > > * Logger API improvement to respect the hierarchy
> > > * Request/response trace logs are now JSON-formatted
> > > * New API to add and remove Streams threads while running
> > > * New REST API to expose Connect task configurations
> > > * Fixed the TimeWindowDeserializer to be able to deserialize
> > > keys outside of Streams (such as in the console consumer)
> > > * Streams resilient improvement: new uncaught exception
> > > handler
> > > * Streams resilience improvement: automatically recover from
> > > transient timeout exceptions
> > >
> > >
> > >
> > >
> > > Release notes for the 2.8.0 release:
> > > https://home.apache.org/~vvcephei/kafka-2.8.0-rc1/RELEASE_NOTES.html
> > >
> > >
> > > *** Please download, test and vote by 6 April 2021 ***
> > >
> > > Kafka's KEYS file containing PGP keys we use to sign the
> > > release:
> > > https://kafka.apache.org/KEYS
> > >
> > > * Release artifacts to be voted upon (source and binary):
> > >
> > > https://home.apache.org/~vvcephei/kafka-2.8.0-rc1/
> > >
> > > * Maven artifacts to be voted upon:
> > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >
> > > * Javadoc:
> > >
> > > https://home.apache.org/~vvcephei/kafka-2.8.0-rc1/javadoc/
> > >
> > > * Tag to be voted upon (off 2.8 branch) is the 2.8.0 tag:
> > >
> > > https://github.com/apache/kafka/releases/tag/2.8.0-rc1
> > >
> > > * Documentation:
> > > https://kafka.apache.org/28/documentation.html
> > >
> > > * Protocol:
> > > https://kafka.apache.org/28/protocol.html
> > >
> > >
> > > /**
> > >
> > > Thanks,
> > > John
> > >
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "kafka-clients" group.
> > > To unsubscribe from this group and stop receiving emails from it, send
> an
> > > email to kafka-clients+unsubscr...@googlegroups.com.
> > > To view this discussion on the web visit
> > >
> https://groups.google.com/d/msgid/kafka-clients/b0814d6acb8f37e0e729e3582bc5552fa30ca8e3.camel%40apache.org
> > > .
> > >
>
>
>

[jira] [Resolved] (KAFKA-12568) Remove deprecated "KStream#groupBy/join", "Joined#named" overloads

[Guozhang Wang (Jira)]

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

Guozhang Wang resolved KAFKA-12568.
---
Fix Version/s: 3.0.0
 Assignee: Guozhang Wang
   Resolution: Fixed

> Remove deprecated "KStream#groupBy/join", "Joined#named" overloads
> --
>
> Key: KAFKA-12568
> URL: https://issues.apache.org/jira/browse/KAFKA-12568
> Project: Kafka
>  Issue Type: Sub-task
>  Components: streams
>Reporter: Guozhang Wang
>Assignee: Guozhang Wang
>Priority: Major
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [kafka-clients] Subject: [VOTE] 2.8.0 RC1

[John Roesler]

Ah, thank you for pointing that out, Israel!

Indeed, I neglected to update the date. Yes, let us say
Tuesday, 13 April 2021 for the testing deadline.

Thanks as well for validating the release!
-John

On Wed, 2021-04-07 at 16:50 -0400, Israel Ekpo wrote:
> Hello John,
> 
> Thanks for running the release for 2.8.0
> 
> I was reviewing the request for validation for 2.8.0 RC1 it appears that
> the deadline to complete testing/validation by the community is 6th April
> 2021
> 
> Same day delivery :)
> 
> I think you meant to say Tuesday, April 13 2021 instead.
> 
> Could we assume that was just a carry over from the previous solicitation
> for 2.8.0 RC0 and you actually meant to say 2021-04-13?
> 
> When you have a moment, please clarify.
> 
> I am running my tests shortly and will share my results by the end of the
> week.
> 
> Thanks.
> 
> 
> 
> On Tue, Apr 6, 2021 at 5:37 PM John Roesler  wrote:
> 
> > Hello Kafka users, developers and client-developers,
> > 
> > This is the second candidate for release of Apache Kafka
> > 2.8.0. This is a major release that includes many new
> > features, including:
> > 
> > * Early-access release of replacing Zookeeper with a self-
> > managed quorum
> > * Add Describe Cluster API
> > * Support mutual TLS authentication on SASL_SSL listeners
> > * Ergonomic improvements to Streams TopologyTestDriver
> > * Logger API improvement to respect the hierarchy
> > * Request/response trace logs are now JSON-formatted
> > * New API to add and remove Streams threads while running
> > * New REST API to expose Connect task configurations
> > * Fixed the TimeWindowDeserializer to be able to deserialize
> > keys outside of Streams (such as in the console consumer)
> > * Streams resilient improvement: new uncaught exception
> > handler
> > * Streams resilience improvement: automatically recover from
> > transient timeout exceptions
> > 
> > 
> > 
> > 
> > Release notes for the 2.8.0 release:
> > https://home.apache.org/~vvcephei/kafka-2.8.0-rc1/RELEASE_NOTES.html
> > 
> > 
> > *** Please download, test and vote by 6 April 2021 ***
> > 
> > Kafka's KEYS file containing PGP keys we use to sign the
> > release:
> > https://kafka.apache.org/KEYS
> > 
> > * Release artifacts to be voted upon (source and binary):
> > 
> > https://home.apache.org/~vvcephei/kafka-2.8.0-rc1/
> > 
> > * Maven artifacts to be voted upon:
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > 
> > * Javadoc:
> > 
> > https://home.apache.org/~vvcephei/kafka-2.8.0-rc1/javadoc/
> > 
> > * Tag to be voted upon (off 2.8 branch) is the 2.8.0 tag:
> > 
> > https://github.com/apache/kafka/releases/tag/2.8.0-rc1
> > 
> > * Documentation:
> > https://kafka.apache.org/28/documentation.html
> > 
> > * Protocol:
> > https://kafka.apache.org/28/protocol.html
> > 
> > 
> > /**
> > 
> > Thanks,
> > John
> > 
> > 
> > 
> > --
> > You received this message because you are subscribed to the Google Groups
> > "kafka-clients" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to kafka-clients+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/kafka-clients/b0814d6acb8f37e0e729e3582bc5552fa30ca8e3.camel%40apache.org
> > .
> > 

Re: [DISCUSS] KIP-729 Custom validation of records on the broker prior to log append

[Soumyajit Sahu]

Thanks Colin! Good call on the ApiRecordError. We could use
InvalidRecordException instead, and have the broker convert it
to ApiRecordError.
Modified signature below.

interface BrokerRecordValidator {
   /**
* Validate the record for a given topic-partition.
*/
Optional validateRecord(TopicPartition
topicPartition, ByteBuffer key, ByteBuffer value, Header[] headers);
}

On Tue, Apr 6, 2021 at 5:09 PM Colin McCabe  wrote:

> Hi Soumyajit,
>
> The difficult thing is deciding which fields to share and how to share
> them.  Key and value are probably the minimum we need to make this useful.
> If we do choose to go with byte buffer, it is not necessary to also pass
> the size, since ByteBuffer maintains that internally.
>
> ApiRecordError is also an internal class, so it can't be used in a public
> API.  I think most likely if we were going to do this, we would just catch
> an exception and use the exception text as the validation error.
>
> best,
> Colin
>
>
> On Tue, Apr 6, 2021, at 15:57, Soumyajit Sahu wrote:
> > Hi Tom,
> >
> > Makes sense. Thanks for the explanation. I get what Colin had meant
> earlier.
> >
> > Would a different signature for the interface work? Example below, but
> > please feel free to suggest alternatives if there are any possibilities
> of
> > such.
> >
> > If needed, then deprecating this and introducing a new signature would be
> > straight-forward as both (old and new) calls could be made serially in
> the
> > LogValidator allowing a coexistence for a transition period.
> >
> > interface BrokerRecordValidator {
> > /**
> >  * Validate the record for a given topic-partition.
> >  */
> > Optional validateRecord(TopicPartition
> topicPartition,
> > int keySize, ByteBuffer key, int valueSize, ByteBuffer value, Header[]
> > headers);
> > }
> >
> >
> > On Tue, Apr 6, 2021 at 12:54 AM Tom Bentley  wrote:
> >
> > > Hi Soumyajit,
> > >
> > > Although that class does indeed have public access at the Java level,
> it
> > > does so only because it needs to be used by internal Kafka code which
> lives
> > > in other packages (there isn't any more restrictive access modifier
> which
> > > would work). What the project considers public Java API is determined
> by
> > > what's included in the published Javadocs:
> > > https://kafka.apache.org/27/javadoc/index.html, which doesn't include
> the
> > > org.apache.kafka.common.record package.
> > >
> > > One of the problems with making these internal classes public is it
> ties
> > > the project into supporting them as APIs, which can make changing them
> much
> > > harder and in the long run that can slow, or even prevent, innovation
> in
> > > the rest of Kafka.
> > >
> > > Kind regards,
> > >
> > > Tom
> > >
> > >
> > >
> > > On Sun, Apr 4, 2021 at 7:31 PM Soumyajit Sahu <
> soumyajit.s...@gmail.com>
> > > wrote:
> > >
> > > > Hi Colin,
> > > > I see that both the interface "Record" and the implementation
> > > > "DefaultRecord" being used in LogValidator.java are public
> > > > interfaces/classes.
> > > >
> > > >
> > > >
> > >
> https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/common/record/Records.java
> > > > and
> > > >
> > > >
> > >
> https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/common/record/DefaultRecord.java
> > > >
> > > > So, it should be ok to use them. Let me know what you think.
> > > >
> > > > Thanks,
> > > > Soumyajit
> > > >
> > > >
> > > > On Fri, Apr 2, 2021 at 8:51 AM Colin McCabe 
> wrote:
> > > >
> > > > > Hi Soumyajit,
> > > > >
> > > > > I believe we've had discussions about proposals similar to this
> before,
> > > > > although I'm having trouble finding one right now.  The issue here
> is
> > > > that
> > > > > Record is a private class -- it is not part of any public API, and
> may
> > > > > change at any time.  So we can't expose it in public APIs.
> > > > >
> > > > > best,
> > > > > Colin
> > > > >
> > > > >
> > > > > On Thu, Apr 1, 2021, at 14:18, Soumyajit Sahu wrote:
> > > > > > Hello All,
> > > > > > I would like to start a discussion on the KIP-729.
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-729%3A+Custom+validation+of+records+on+the+broker+prior+to+log+append
> > > > > >
> > > > > > Thanks!
> > > > > > Soumyajit
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Committer: Bruno Cadonna

[Bill Bejeck]

Congrats Bruno! Well deserved.

Bill

On Wed, Apr 7, 2021 at 6:34 PM Guozhang Wang  wrote:

> Hello all,
>
> I'm happy to announce that Bruno Cadonna has accepted his invitation to
> become an Apache Kafka committer.
>
> Bruno has been contributing to Kafka since Jan. 2019 and has made 99
> commits and more than 80 PR reviews so far:
>
> https://github.com/apache/kafka/commits?author=cadonna
>
> He worked on a few key KIPs on Kafka Streams:
>
> * KIP-471: Expose RocksDB Metrics in Kafka Streams
> * KIP-607: Add Metrics to Kafka Streams to Report Properties of RocksDB
> * KIP-662: Throw Exception when Source Topics of a Streams App are Deleted
>
> Besides all the code contributions and reviews, he's also done a handful
> for the community: multiple Kafka meetup talks in Berlin and Kafka Summit
> talks, an introductory class to Kafka at Humboldt-Universität zu Berlin
> seminars, and have co-authored a paper on Kafka's stream processing
> semantics in this year's SIGMOD conference (
> https://en.wikipedia.org/wiki/SIGMOD). Bruno has also been quite active on
> SO channels and AK mailings.
>
> Please join me to congratulate Bruno for all the contributions!
>
> -- Guozhang
>

[ANNOUNCE] New Committer: Bruno Cadonna

[Guozhang Wang]

Hello all,

I'm happy to announce that Bruno Cadonna has accepted his invitation to
become an Apache Kafka committer.

Bruno has been contributing to Kafka since Jan. 2019 and has made 99
commits and more than 80 PR reviews so far:

https://github.com/apache/kafka/commits?author=cadonna

He worked on a few key KIPs on Kafka Streams:

* KIP-471: Expose RocksDB Metrics in Kafka Streams
* KIP-607: Add Metrics to Kafka Streams to Report Properties of RocksDB
* KIP-662: Throw Exception when Source Topics of a Streams App are Deleted

Besides all the code contributions and reviews, he's also done a handful
for the community: multiple Kafka meetup talks in Berlin and Kafka Summit
talks, an introductory class to Kafka at Humboldt-Universität zu Berlin
seminars, and have co-authored a paper on Kafka's stream processing
semantics in this year's SIGMOD conference (
https://en.wikipedia.org/wiki/SIGMOD). Bruno has also been quite active on
SO channels and AK mailings.

Please join me to congratulate Bruno for all the contributions!

-- Guozhang

[jira] [Created] (KAFKA-12631) Support api to resign raft leadership

[Jason Gustafson (Jira)]

Jason Gustafson created KAFKA-12631:
---

 Summary: Support api to resign raft leadership
 Key: KAFKA-12631
 URL: https://issues.apache.org/jira/browse/KAFKA-12631
 Project: Kafka
  Issue Type: Sub-task
Reporter: Jason Gustafson


It is useful to allow the controller to explicitly resign after encountering an 
error of some kind. The Raft state machine implements a Resigned state, but it 
is only currently used during graceful shutdown.

This work depends on both of the following jiras:

- KAFKA-12342: Adds resign() api after merging MetaLogManager interface
- KAFKA-12607: Adds support for granting votes while in the Resigned state



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KAFKA-12630) Remove deprecated KafkaClientSupplier#getAdminClient

[Guozhang Wang (Jira)]

Guozhang Wang created KAFKA-12630:
-

 Summary: Remove deprecated KafkaClientSupplier#getAdminClient
 Key: KAFKA-12630
 URL: https://issues.apache.org/jira/browse/KAFKA-12630
 Project: Kafka
  Issue Type: Sub-task
Reporter: Guozhang Wang
Assignee: Guozhang Wang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [kafka-clients] Subject: [VOTE] 2.8.0 RC1

[Israel Ekpo]

Hello John,

Thanks for running the release for 2.8.0

I was reviewing the request for validation for 2.8.0 RC1 it appears that
the deadline to complete testing/validation by the community is 6th April
2021

Same day delivery :)

I think you meant to say Tuesday, April 13 2021 instead.

Could we assume that was just a carry over from the previous solicitation
for 2.8.0 RC0 and you actually meant to say 2021-04-13?

When you have a moment, please clarify.

I am running my tests shortly and will share my results by the end of the
week.

Thanks.



On Tue, Apr 6, 2021 at 5:37 PM John Roesler  wrote:

> Hello Kafka users, developers and client-developers,
>
> This is the second candidate for release of Apache Kafka
> 2.8.0. This is a major release that includes many new
> features, including:
>
> * Early-access release of replacing Zookeeper with a self-
> managed quorum
> * Add Describe Cluster API
> * Support mutual TLS authentication on SASL_SSL listeners
> * Ergonomic improvements to Streams TopologyTestDriver
> * Logger API improvement to respect the hierarchy
> * Request/response trace logs are now JSON-formatted
> * New API to add and remove Streams threads while running
> * New REST API to expose Connect task configurations
> * Fixed the TimeWindowDeserializer to be able to deserialize
> keys outside of Streams (such as in the console consumer)
> * Streams resilient improvement: new uncaught exception
> handler
> * Streams resilience improvement: automatically recover from
> transient timeout exceptions
>
>
>
>
> Release notes for the 2.8.0 release:
> https://home.apache.org/~vvcephei/kafka-2.8.0-rc1/RELEASE_NOTES.html
>
>
> *** Please download, test and vote by 6 April 2021 ***
>
> Kafka's KEYS file containing PGP keys we use to sign the
> release:
> https://kafka.apache.org/KEYS
>
> * Release artifacts to be voted upon (source and binary):
>
> https://home.apache.org/~vvcephei/kafka-2.8.0-rc1/
>
> * Maven artifacts to be voted upon:
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>
> * Javadoc:
>
> https://home.apache.org/~vvcephei/kafka-2.8.0-rc1/javadoc/
>
> * Tag to be voted upon (off 2.8 branch) is the 2.8.0 tag:
>
> https://github.com/apache/kafka/releases/tag/2.8.0-rc1
>
> * Documentation:
> https://kafka.apache.org/28/documentation.html
>
> * Protocol:
> https://kafka.apache.org/28/protocol.html
>
>
> /**
>
> Thanks,
> John
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "kafka-clients" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kafka-clients+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/kafka-clients/b0814d6acb8f37e0e729e3582bc5552fa30ca8e3.camel%40apache.org
> .
>

[jira] [Resolved] (KAFKA-7785) Remove PartitionGrouper interface and it's config and move DefaultPartitionGrouper to internal package

[Guozhang Wang (Jira)]

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

Guozhang Wang resolved KAFKA-7785.
--
Resolution: Fixed

> Remove PartitionGrouper interface and it's config and move 
> DefaultPartitionGrouper to internal package
> --
>
> Key: KAFKA-7785
> URL: https://issues.apache.org/jira/browse/KAFKA-7785
> Project: Kafka
>  Issue Type: Sub-task
>  Components: streams
>Affects Versions: 2.1.0
>Reporter: Jacek Laskowski
>Assignee: highluck
>Priority: Blocker
> Fix For: 3.0.0
>
>
> Since {{DefaultPartitionGrouper}} is only for the purpose of the internal 
> {{StreamsPartitionAssignor}} it would make sense to have it in the 
> {{org.apache.kafka.streams.processor.internals}} package.
> I would also vote to move {{PartitionGrouper.}}
> Via KAFKA-8927 we deprecated the `PartitionGrouper` interface in 2.4 release 
> – this allows us to remove the public interface and its corresponding config 
> in the next major release (ie, 3.0.0). `DefaultPartitionGrouper` was 
> implicitly deprecated via KAFKA-8927.
> Hence, we can move the interface as well as the default implementation into 
> an internal package (or maybe just remove the interface completely as there 
> are no plans to support multiple implementations atm).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] Please review 2.8.0 blog post

[John Roesler]

Thanks for that catch, Tom!

I was trying to use the permalinks, but I must have let that
one slip though. I'll go back and do an audit.

I really appreciate it,
-John

On Wed, 2021-04-07 at 16:58 +0100, Tom Bentley wrote:
> Hi John,
> 
> I think the link to the KIP-500 README file might be a broken link, since
> the directory got renamed from self-managed to kraft.
> 
> Kind regards,
> 
> Tom
> 
> 
> On Tue, Apr 6, 2021 at 4:06 AM Sagar  wrote:
> 
> > Got it, Thanks for the explanation John!
> > 
> > Thanks!
> > Sagar.
> > 
> > On Tue, Apr 6, 2021 at 8:16 AM John Roesler  wrote:
> > 
> > > Oh, my apologies, Sagar,
> > > 
> > > That link will not resolve until the release. The release
> > > notes that I prepared as part of the RC are available here:
> > > https://home.apache.org/~vvcephei/kafka-2.8.0-rc0/RELEASE_NOTES.html
> > > 
> > > I used the post-release link because I didn't want to forget
> > > it, but now I see how that would be unexpected as a
> > > reviewer. I should have mentioned it in my first email.
> > > 
> > > Along the same lines, the video link will also not be live
> > > until the release.
> > > 
> > > Thank you for taking a look!
> > > 
> > > -John
> > > 
> > > On Tue, 2021-04-06 at 07:45 +0530, Sagar wrote:
> > > > Hi,
> > > > 
> > > > I am not sure if others are experiencing it, but when I click on the
> > > > Release notes link provided on the page, it keeps throwing 404:
> > > > 
> > > > 
> > > 
> > https://dist.apache.org/repos/dist/release/kafka/2.8.0/RELEASE_NOTES.html
> > > > 
> > > > Not sure if its an issue but thought I will call it out :D
> > > > 
> > > > Thanks!
> > > > Sagar.
> > > > 
> > > > On Mon, Apr 5, 2021 at 6:29 PM Adam Bellemare <
> > adam.bellem...@gmail.com>
> > > > wrote:
> > > > 
> > > > > Read it all. It looks good to me in terms of structure and content. I
> > > am
> > > > > not sufficiently up to date on all the features that are otherwise
> > > included
> > > > > in 2.8.0, but the ones listed seem very prominent!
> > > > > 
> > > > > 
> > > > > 
> > > > > On Thu, Apr 1, 2021 at 4:39 PM John Roesler 
> > > wrote:
> > > > > 
> > > > > > Hello all,
> > > > > > 
> > > > > > In the steady march toward the Apache Kafka 2.8.0 release, I
> > > > > > have prepared a draft of the release announcement post:
> > > > > > 
> > > > > > 
> > > > > 
> > > 
> > https://blogs.apache.org/preview/kafka/?previewEntry=what-s-new-in-apache5
> > > > > > 
> > > > > > If you have a moment, I would greatly appreciate your
> > > > > > reviews.
> > > > > > 
> > > > > > Thank you,
> > > > > > -John
> > > > > > 
> > > > > > 
> > > > > 
> > > 
> > > 
> > > 
> > 

[jira] [Created] (KAFKA-12629) Flaky Test RaftClusterTest

[Matthias J. Sax (Jira)]

Matthias J. Sax created KAFKA-12629:
---

 Summary: Flaky Test RaftClusterTest
 Key: KAFKA-12629
 URL: https://issues.apache.org/jira/browse/KAFKA-12629
 Project: Kafka
  Issue Type: Test
  Components: core, unit tests
Reporter: Matthias J. Sax


{quote} {{java.util.concurrent.ExecutionException: 
java.lang.ClassNotFoundException: 
org.apache.kafka.controller.NoOpSnapshotWriterBuilder
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at 
kafka.testkit.KafkaClusterTestKit.startup(KafkaClusterTestKit.java:364)
at 
kafka.server.RaftClusterTest.testCreateClusterAndCreateAndManyTopicsWithManyPartitions(RaftClusterTest.scala:181)}}{quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] KIP-693: Client-side Circuit Breaker for Partition Write Errors

[Jun Rao]

Hi, George,

A few more comments on the KIP.

1. It would be useful to motivate the problem a bit more. For example, is
the KIP trying to solve a transient broker problem (if so, for how long) or
a permanent broker problem? It would also be useful to list some common
causes that can slow the broker down.

2. It would be useful to discuss a bit more on the high level approach
(e.g. in the rejected section). This KIP proposes to fix the issue on the
client side by having a pluggable component to redirect the traffic to
other brokers. One potential issue with this is that it requires all
clients to opt in (assuming this is not the default) for the plugin to see
the benefit. In some environments with a large number of clients,
coordinating all those clients may not be easy. Another potential solution
is to fix the issue on the server side. For example, if a broker is slow
because it has noisy neighbors in a virtual environment, we could
proactively bring down the broker and restart it somewhere else. This has
the benefit that it requires less client side coordination.

3. Regarding how to detect broker slowness in the client. The proposal is
based on the error in the produce response. Typically, if the broker is
just slow, the only type of error the client gets is the timeout exception.
Since the default timeout is 30 seconds, it may not be triggered all the
time and it may be too late to reflect a broker side issue. I am wondering
if there are other better indicators. For example, another potential option
is to use the number of pending batches per partition (or broker) in the
Accumulator. Intuitively, if a broker is slow, all partitions with the
leader on it will gradually accumulate more batches.

4. It would be useful to have a solution that works with keyed messages so
that they can still be distributed to the partition based on the hash of
the key.

Thanks,

Jun


On Wed, Mar 24, 2021 at 4:05 AM Guoqiang Shu  wrote:

>
> In our current proposal it can be configured via
> producer.circuit.breaker.mute.retry.interval (defaulted to 10 mins), but
> perhaps 'interval' is a confusing name.
>
> On 2021/03/23 00:45:23, Guozhang Wang  wrote:
> > Thanks for the updated KIP! Some more comments inlined.
> > >
> > > I'm still not sure if, in your proposal, the muting length is a
> > customizable value (and if yes, through which config) or it is always
> hard
> > coded as 10 minutes?
> >
> >
> > > > Guozhang
>
>

[jira] [Created] (KAFKA-12628) SSL context is never re-evaluate by consumer or producer

[raphael auv (Jira)]

raphael auv created KAFKA-12628:
---

 Summary: SSL context is never re-evaluate by consumer or producer
 Key: KAFKA-12628
 URL: https://issues.apache.org/jira/browse/KAFKA-12628
 Project: Kafka
  Issue Type: Improvement
Affects Versions: 2.7.0
Reporter: raphael auv


*SslChannelBuilder reconfigure is never call*

The reconfigure function is never call 

[https://github.com/apache/kafka/blob/fe1804370680b965a68fdd2978e2afa450daafe4/clients/src/main/java/org/apache/kafka/common/network/SslChannelBuilder.java#L91]

That mean that the SSL context ( keystore file or trustore file changes ) is 
never re-evaluate at run time of the consumer or producers.

So the code checking if there is a new SSL context is never call

https://github.com/apache/kafka/blob/fe1804370680b965a68fdd2978e2afa450daafe4/clients/src/main/java/org/apache/kafka/common/security/ssl/SslFactory.java#L121



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] Please review 2.8.0 blog post

[Tom Bentley]

Hi John,

I think the link to the KIP-500 README file might be a broken link, since
the directory got renamed from self-managed to kraft.

Kind regards,

Tom


On Tue, Apr 6, 2021 at 4:06 AM Sagar  wrote:

> Got it, Thanks for the explanation John!
>
> Thanks!
> Sagar.
>
> On Tue, Apr 6, 2021 at 8:16 AM John Roesler  wrote:
>
> > Oh, my apologies, Sagar,
> >
> > That link will not resolve until the release. The release
> > notes that I prepared as part of the RC are available here:
> > https://home.apache.org/~vvcephei/kafka-2.8.0-rc0/RELEASE_NOTES.html
> >
> > I used the post-release link because I didn't want to forget
> > it, but now I see how that would be unexpected as a
> > reviewer. I should have mentioned it in my first email.
> >
> > Along the same lines, the video link will also not be live
> > until the release.
> >
> > Thank you for taking a look!
> >
> > -John
> >
> > On Tue, 2021-04-06 at 07:45 +0530, Sagar wrote:
> > > Hi,
> > >
> > > I am not sure if others are experiencing it, but when I click on the
> > > Release notes link provided on the page, it keeps throwing 404:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/release/kafka/2.8.0/RELEASE_NOTES.html
> > >
> > > Not sure if its an issue but thought I will call it out :D
> > >
> > > Thanks!
> > > Sagar.
> > >
> > > On Mon, Apr 5, 2021 at 6:29 PM Adam Bellemare <
> adam.bellem...@gmail.com>
> > > wrote:
> > >
> > > > Read it all. It looks good to me in terms of structure and content. I
> > am
> > > > not sufficiently up to date on all the features that are otherwise
> > included
> > > > in 2.8.0, but the ones listed seem very prominent!
> > > >
> > > >
> > > >
> > > > On Thu, Apr 1, 2021 at 4:39 PM John Roesler 
> > wrote:
> > > >
> > > > > Hello all,
> > > > >
> > > > > In the steady march toward the Apache Kafka 2.8.0 release, I
> > > > > have prepared a draft of the release announcement post:
> > > > >
> > > > >
> > > >
> >
> https://blogs.apache.org/preview/kafka/?previewEntry=what-s-new-in-apache5
> > > > >
> > > > > If you have a moment, I would greatly appreciate your
> > > > > reviews.
> > > > >
> > > > > Thank you,
> > > > > -John
> > > > >
> > > > >
> > > >
> >
> >
> >
>

[jira] [Resolved] (KAFKA-12626) RaftClusterTest and ClusterTestExtensionTest failures

[Ismael Juma (Jira)]

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

Ismael Juma resolved KAFKA-12626.
-
  Assignee: Colin McCabe
Resolution: Fixed

> RaftClusterTest and ClusterTestExtensionTest failures
> -
>
> Key: KAFKA-12626
> URL: https://issues.apache.org/jira/browse/KAFKA-12626
> Project: Kafka
>  Issue Type: Bug
>Reporter: Justine Olshan
>Assignee: Colin McCabe
>Priority: Major
>
> RaftClusterTest and ClusterTestExtensionsTest.[Quorum 2] 
> Name=cluster-tests-2, security=PLAINTEXT are failing due to
> {noformat}
> java.util.concurrent.ExecutionException: java.lang.ClassNotFoundException: 
> org.apache.kafka.controller.NoOpSnapshotWriterBuilder{noformat}
> I think it is related to the changes from 
> [https://github.com/apache/kafka/commit/7bc84d6ced71056dbb4cecdc9abbdbd7d8a5aa10#diff-77dc2adb187fd078084644613cff2b53021c8a5fbcdcfa116515734609d1332aR210]
>  specifically this part of the code 
> [https://github.com/apache/kafka/blob/33d0445b8408289800352de7822340028782a154/metadata/src/main/java/org/apache/kafka/controller/QuorumController.java#L210]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] KIP-730: Producer ID generation in KRaft mode

[Ron Dagostino]

Thanks for the KIP, David.

With the RPC returning a start and length, should the record in the
metadata log do the same thing for consistency and to save the byte
per record?

Ron


On Tue, Apr 6, 2021 at 11:06 PM Ismael Juma  wrote:
>
> Great, thanks. Instead of calling it "bridge release", can we say 3.0?
>
> Ismael
>
> On Tue, Apr 6, 2021 at 7:48 PM David Arthur  wrote:
>
> > Thanks for the feedback, Ismael. Renaming the RPC and using start+len
> > instead of start+end sounds fine.
> >
> > And yes, the controller will allocate the IDs in ZK mode for the bridge
> > release.
> >
> > I'll update the KIP to reflect these points.
> >
> > Thanks!
> >
> > On Tue, Apr 6, 2021 at 7:30 PM Ismael Juma  wrote:
> >
> > > Sorry, one more question: the allocation of ids will be done by the
> > > controller even in ZK mode, right?
> > >
> > > Ismael
> > >
> > > On Tue, Apr 6, 2021 at 4:26 PM Ismael Juma  wrote:
> > >
> > > > One additional comment: if you return the number of ids instead of the
> > > end
> > > > range, you can use an int32.
> > > >
> > > > Ismael
> > > >
> > > > On Tue, Apr 6, 2021 at 4:25 PM Ismael Juma  wrote:
> > > >
> > > >> Thanks for the KIP, David. Any reason not to rename
> > > >> AllocateProducerIdBlockRequest to AllocateProducerIdsRequest?
> > > >>
> > > >> Ismael
> > > >>
> > > >> On Tue, Apr 6, 2021 at 3:51 PM David Arthur  wrote:
> > > >>
> > > >>> Hello everyone,
> > > >>>
> > > >>> I'd like to start the discussion for KIP-730
> > > >>>
> > > >>>
> > > >>>
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-730%3A+Producer+ID+generation+in+KRaft+mode
> > > >>>
> > > >>> This KIP proposes a new RPC for generating blocks of IDs for
> > > >>> transactional
> > > >>> and idempotent producers.
> > > >>>
> > > >>> Cheers,
> > > >>> David Arthur
> > > >>>
> > > >>
> > >
> >
> >
> > --
> > David Arthur
> >

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #13

[Apache Jenkins Server]

See