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

[Apache Jenkins Server]

See 

[jira] [Created] (KAFKA-12707) KafkaProducer should have a clearer error message on sasl.mechanism misconfiguration

[Rohan Desai (Jira)]

Rohan Desai created KAFKA-12707:
---

 Summary: KafkaProducer should have a clearer error message on 
sasl.mechanism misconfiguration
 Key: KAFKA-12707
 URL: https://issues.apache.org/jira/browse/KAFKA-12707
 Project: Kafka
  Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Rohan Desai


Not sure if this is producer-specific, but I accidentally configured my 
producer by setting:

```

sasl.mechanism=plain

```

instead of 

```

sasl.mechanism=PLAIN

```

 

When I did this, the producer just hangs and logs in a loop like this, which 
isn't very informative:
[2021-04-21 21:33:20,519] WARN [Producer clientId=producer-1] Bootstrap broker 
pkc-g91q1.us-west-2.aws.stag.cpdev.cloud:9092 (id: -1 rack: null) disconnected 
(org.apache.kafka.clients.NetworkClient:1050)
[2021-04-21 21:33:21,584] INFO [Producer clientId=producer-1] Failed to create 
channel due to  (org.apache.kafka.common.network.SaslChannelBuilder:239)
org.apache.kafka.common.errors.SaslAuthenticationException: Failed to configure 
SaslClientAuthenticator
Caused by: org.apache.kafka.common.errors.SaslAuthenticationException: Failed 
to create SaslClient with mechanism plain
[2021-04-21 21:33:21,584] WARN [Producer clientId=producer-1] Error connecting 
to node pkc-g91q1.us-west-2.aws.stag.cpdev.cloud:9092 (id: -1 rack: null) 
(org.apache.kafka.clients.NetworkClient:982)
java.io.IOException: Channel could not be created for socket 
java.nio.channels.SocketChannel[closed]
at 
org.apache.kafka.common.network.Selector.buildAndAttachKafkaChannel(Selector.java:348)
at 
org.apache.kafka.common.network.Selector.registerChannel(Selector.java:329)
at org.apache.kafka.common.network.Selector.connect(Selector.java:256)
at 
org.apache.kafka.clients.NetworkClient.initiateConnect(NetworkClient.java:977)
at 
org.apache.kafka.clients.NetworkClient.access$600(NetworkClient.java:73)
at 
org.apache.kafka.clients.NetworkClient$DefaultMetadataUpdater.maybeUpdate(NetworkClient.java:1148)
at 
org.apache.kafka.clients.NetworkClient$DefaultMetadataUpdater.maybeUpdate(NetworkClient.java:1036)
at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:549)
at 
org.apache.kafka.clients.producer.internals.Sender.runOnce(Sender.java:328)
at 
org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:243)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.kafka.common.KafkaException: 
org.apache.kafka.common.errors.SaslAuthenticationException: Failed to configure 
SaslClientAuthenticator
at 
org.apache.kafka.common.network.SaslChannelBuilder.buildChannel(SaslChannelBuilder.java:240)
at 
org.apache.kafka.common.network.Selector.buildAndAttachKafkaChannel(Selector.java:338)
... 10 more
Caused by: org.apache.kafka.common.errors.SaslAuthenticationException: Failed 
to configure SaslClientAuthenticator
Caused by: org.apache.kafka.common.errors.SaslAuthenticationException: Failed 
to create SaslClient with mechanism plain
[2021-04-21 21:33:21,584] WARN [Producer clientId=producer-1] Bootstrap broker 
pkc-g91q1.us-west-2.aws.stag.cpdev.cloud:9092 (id: -1 rack: null) disconnected 
(org.apache.kafka.clients.NetworkClient:1050)
 

It would be better to early-exit with a clear error message



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

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

[Navinder Brar]

Congrats Bill, very well deserved!

Regards,Navinder Pal Singh BrarLinkedIn
 

On Wednesday, 21 April, 2021, 10:37:53 pm IST, Sarwar Bhuiyan 
 wrote:  
 
 Congrats Bill!

On Wed, Apr 21, 2021 at 5:52 PM Mickael Maison 
wrote:

> Congratulations Bill, well deserved!
>
> On Sat, Apr 17, 2021 at 11:26 PM Adam Bellemare
>  wrote:
> >
> > Congratulations Bill!!
> >
> > > On Apr 17, 2021, at 5:20 PM, Kowshik Prakasam 
> > > 
> wrote:
> > >
> > > Congrats Bill!
> > >
> > >
> > > Cheers,
> > > Kowshik
> > >
> > >> On Mon, Apr 12, 2021, 11:15 AM Randall Hauch 
> wrote:
> > >>
> > >> Congratulations, Bill!
> > >>
> > >>> On Mon, Apr 12, 2021 at 11:02 AM Guozhang Wang 
> wrote:
> > >>>
> > >>> Congratulations Bill !
> > >>>
> > >>> Guozhang
> > >>>
> >  On Wed, Apr 7, 2021 at 6:16 PM 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
> > 
> > >>>
> > >>>
> > >>> --
> > >>> -- Guozhang
> > >>>
> > >>
>
  

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

[Apache Jenkins Server]

See 

[jira] [Resolved] (KAFKA-12621) Kafka setup with Zookeeper- specifying an alternate znode creates the configuration at the wrong znode

[Jibitesh Prasad (Jira)]

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

Jibitesh Prasad resolved KAFKA-12621.
-
Resolution: Fixed

Incorrect configuration on my part

> Kafka setup with Zookeeper- specifying an alternate znode creates the 
> configuration at the wrong znode
> --
>
> Key: KAFKA-12621
> URL: https://issues.apache.org/jira/browse/KAFKA-12621
> Project: Kafka
>  Issue Type: Bug
>  Components: config
>Affects Versions: 2.6.1
> Environment: Linux
> OS: 16.04.1-Ubuntu SMP 
> Architecture: x86_64
> Kernel Version: 4.15.0-1108-azure
>Reporter: Jibitesh Prasad
>Priority: Major
>  Labels: config, newbie, server.properties
>
> While configuring kafka with an znode apart from "/", the configuration is 
> created in the wrong znode. Fo example, I have the following entry in my 
> server.properties
> _zookeeper.connect=10.114.103.207:2181/kafka_secondary_cluster,10.114.103.206:2181/kafka_secondary_cluster,10.114.103.205:2181/kafka_secondary_cluster_
> The IPs are the IP addresses of the nodes of zookeeper cluster. I expect the 
> kafka server to use _kafka_secondary_cluster_ as the znode in the zookeeper 
> nodes. But, the znode which is created is actually
> _/kafka_secondary_cluster,10.114.103.206:2181/kafka_secondary_cluster,10.114.103.205:2181/kafka_secondary_cluster_
> Executing ls on the above path shows me the necessary znodes being created in 
> that path
> _[zk: localhost:2181(CONNECTED) 1] ls 
> /kafka_secondary_cluster,10.114.103.206:2181/kafka_secondary_cluster,10.114.103.205:2181/kafka_secondary_cluster_
> Output:
>  _[admin, brokers, cluster, config, consumers, controller, controller_epoch, 
> isr_change_notification, latest_producer_id_block, 
> log_dir_event_notification]_
> Shouldn't these configurations be created in _/kafka_secondary_cluster_. It 
> seems the comma separated values are not being split correctly. Or am I doing 
> something wrong?



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

Jenkins build is back to normal : Kafka » kafka-2.6-jdk8 #119

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build is back to normal : Kafka » Kafka Branch Builder » 2.8 #19

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

[jira] [Created] (KAFKA-12706) Consider adding reason and source of error in APPLICATION_SHUTDOWN

[A. Sophie Blee-Goldman (Jira)]

A. Sophie Blee-Goldman created KAFKA-12706:
--

 Summary: Consider adding reason and source of error in 
APPLICATION_SHUTDOWN
 Key: KAFKA-12706
 URL: https://issues.apache.org/jira/browse/KAFKA-12706
 Project: Kafka
  Issue Type: Improvement
  Components: streams
Reporter: A. Sophie Blee-Goldman


At the moment when a user opts to shut down the application in the streams 
uncaught exception handler, we just send a signal to all members of the group 
who then shut down. If there are a large number of application instances 
running it can be annoying and time consuming to locate the client that hit 
this error.

It would be nice if we could let each client log the exception that triggered 
this, and possibly also the client who requested the shutdown. That will make 
it much easier to identify the problem, and figure out which set of logs to 
look into for further information



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

Re: [VOTE] 2.7.1 RC2

[Israel Ekpo]

I will build from source tomorrow morning, run validation checks and share
my findings and vote then.

Thanks for the reminder.

On Wed, Apr 21, 2021 at 12:50 PM Mickael Maison 
wrote:

> Bumping this thread
>
> Can we get a few more votes?
>
> Thanks
>
>
> On Thu, Apr 15, 2021 at 5:37 PM Bill Bejeck  wrote:
> >
> > Mickael,
> >
> > Thanks for running the release.
> >
> > I validated the checksums and signatures, built the project from src, and
> > ran the unit tests.
> > I'm +1(binding).
> >
> > -Bill
> >
> > On Wed, Apr 14, 2021 at 7:31 PM John Roesler 
> wrote:
> >
> > > Hi Mickael,
> > >
> > > I verified the signatures and checksums, ran the tests, and
> > > spot-checked the license.
> > >
> > > I'm +1 (binding).
> > >
> > > Thanks for driving this release!
> > > -John
> > >
> > > On Fri, 2021-04-09 at 11:07 +0100, Mickael Maison wrote:
> > > > Hi,
> > > >
> > > > Here is a successful build of 2.7.1 RC2:
> > > > https://ci-builds.apache.org/job/Kafka/job/kafka-2.7-jdk8/144/
> > > >
> > > > Thanks
> > > >
> > > > On Thu, Apr 8, 2021 at 6:27 PM Mickael Maison 
> > > wrote:
> > > > >
> > > > > Hello Kafka users, developers and client-developers,
> > > > >
> > > > > This is the third candidate for release of Apache Kafka 2.7.1.
> > > > >
> > > > > Since 2.7.1 RC1, the following JIRAs have been fixed: KAFKA-12593,
> > > > > KAFKA-12474, KAFKA-12602.
> > > > >
> > > > > Release notes for the 2.7.1 release:
> > > > >
> https://home.apache.org/~mimaison/kafka-2.7.1-rc2/RELEASE_NOTES.html
> > > > >
> > > > > *** Please download, test and vote by Friday, April 16, 5pm BST
> > > > >
> > > > > 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/~mimaison/kafka-2.7.1-rc2/
> > > > >
> > > > > * Maven artifacts to be voted upon:
> > > > >
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > > > >
> > > > > * Javadoc:
> > > > > https://home.apache.org/~mimaison/kafka-2.7.1-rc2/javadoc/
> > > > >
> > > > > * Tag to be voted upon (off 2.7 branch) is the 2.7.1 tag:
> > > > > https://github.com/apache/kafka/releases/tag/2.7.1-rc2
> > > > >
> > > > > * Documentation:
> > > > > https://kafka.apache.org/27/documentation.html
> > > > >
> > > > > * Protocol:
> > > > > https://kafka.apache.org/27/protocol.html
> > > > >
> > > > > * Successful Jenkins builds for the 2.7 branch:
> > > > > The build is still running, I'll update the thread once it's
> complete
> > > > >
> > > > > /**
> > > > >
> > > > > Thanks,
> > > > > Mickael
> > >
> > >
> > >
>

[GitHub] [kafka-site] rhauch merged pull request #350: Changed the 2.6.1 links to use the archives

[GitBox]

rhauch merged pull request #350:
URL: https://github.com/apache/kafka-site/pull/350


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (KAFKA-12705) Task idling is not sufficiently tested

[Walker Carlson (Jira)]

Walker Carlson created KAFKA-12705:
--

 Summary: Task idling is not sufficiently tested
 Key: KAFKA-12705
 URL: https://issues.apache.org/jira/browse/KAFKA-12705
 Project: Kafka
  Issue Type: Improvement
  Components: streams
Reporter: Walker Carlson


The test for task idling are a bit sparse. When I changed it so that 
isProcessable always returns true only one test failed. That means the entire 
code path is hinging on one unit test 
(shouldBeProcessableIfAllPartitionsBuffered) that does not cover all branches 
of logic. 



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

Re: [ANNOUNCE] Apache Kafka 2.6.2

[Bill Bejeck]

Congratulations to the community and thanks to all the contributors.

Thanks for driving the release, Sophie!

-Bill

On Wed, Apr 21, 2021 at 4:49 PM Randall Hauch  wrote:

> Than you for driving this release, Sophie! And thanks to everyone that
> contributed. Congratulations!
>
> Best regards,
>
> Randall
>
> On Wed, Apr 21, 2021 at 3:43 PM Sophie Blee-Goldman <
> ableegold...@apache.org>
> wrote:
>
> > The Apache Kafka community is pleased to announce the release for Apache
> > Kafka 2.6.2
> >
> > This is a bug fix release and it includes fixes and improvements from
> > 35 JIRAs, including a few critical bugs.
> >
> > All of the changes in this release can be found in the release notes:
> > https://www.apache.org/dist/kafka/2.6.2/RELEASE_NOTES.html
> >
> >
> > You can download the source and binary release (Scala 2.12
> > and 2.13) from:
> > https://kafka.apache.org/downloads#2.6.2
> >
> >
> >
> ---
> >
> >
> > Apache Kafka is a distributed streaming platform with four core APIs:
> >
> >
> > ** The Producer API allows an application to publish a stream of records
> to
> > one or more Kafka topics.
> >
> > ** The Consumer API allows an application to subscribe to one or more
> > topics and process the stream of records produced to them.
> >
> > ** The Streams API allows an application to act as a stream processor,
> > consuming an input stream from one or more topics and producing an
> > output stream to one or more output topics, effectively transforming the
> > input streams to output streams.
> >
> > ** The Connector API allows building and running reusable producers or
> > consumers that connect Kafka topics to existing applications or data
> > systems. For example, a connector to a relational database might
> > capture every change to a table.
> >
> >
> > With these APIs, Kafka can be used for two broad classes of application:
> >
> > ** Building real-time streaming data pipelines that reliably get data
> > between systems or applications.
> >
> > ** Building real-time streaming applications that transform or react
> > to the streams of data.
> >
> >
> > Apache Kafka is in use at large and small companies worldwide, including
> > Capital One, Goldman Sachs, ING, LinkedIn, Netflix, Pinterest, Rabobank,
> > Target, The New York Times, Uber, Yelp, and Zalando, among others.
> >
> > A big thank you for the following 26 contributors to this release!
> >
> > A. Sophie Blee-Goldman, Andy Wilkinson, Bob Barrett, Bruno Cadonna,
> > Chia-Ping Tsai, Chris Egerton, dengziming, Greg Harris, Ismael Juma, Jim
> > Galasyn, John Roesler, Julien Jean Paul Sirocchi, Lee Dongjin, Luke Chen,
> > Manikumar Reddy, Matthias J. Sax, Michael G. Noll, Mickael Maison, Rajini
> > Sivaram, Ramesh Krishnan M, Randall Hauch, Sharath Bhat, Stanislav
> > Vodetskyi, Walker Carlson, Yilong Chang
> >
> > We welcome your help and feedback. For more information on how to
> > report problems, and to get involved, visit the project website at
> > https://kafka.apache.org/
> >
> > Thank you!
> >
> >
> > Cheers,
> >
> > Sophie
> >
>

Re: [ANNOUNCE] Apache Kafka 2.6.2

[Randall Hauch]

Than you for driving this release, Sophie! And thanks to everyone that
contributed. Congratulations!

Best regards,

Randall

On Wed, Apr 21, 2021 at 3:43 PM Sophie Blee-Goldman 
wrote:

> The Apache Kafka community is pleased to announce the release for Apache
> Kafka 2.6.2
>
> This is a bug fix release and it includes fixes and improvements from
> 35 JIRAs, including a few critical bugs.
>
> All of the changes in this release can be found in the release notes:
> https://www.apache.org/dist/kafka/2.6.2/RELEASE_NOTES.html
>
>
> You can download the source and binary release (Scala 2.12
> and 2.13) from:
> https://kafka.apache.org/downloads#2.6.2
>
>
> ---
>
>
> Apache Kafka is a distributed streaming platform with four core APIs:
>
>
> ** The Producer API allows an application to publish a stream of records to
> one or more Kafka topics.
>
> ** The Consumer API allows an application to subscribe to one or more
> topics and process the stream of records produced to them.
>
> ** The Streams API allows an application to act as a stream processor,
> consuming an input stream from one or more topics and producing an
> output stream to one or more output topics, effectively transforming the
> input streams to output streams.
>
> ** The Connector API allows building and running reusable producers or
> consumers that connect Kafka topics to existing applications or data
> systems. For example, a connector to a relational database might
> capture every change to a table.
>
>
> With these APIs, Kafka can be used for two broad classes of application:
>
> ** Building real-time streaming data pipelines that reliably get data
> between systems or applications.
>
> ** Building real-time streaming applications that transform or react
> to the streams of data.
>
>
> Apache Kafka is in use at large and small companies worldwide, including
> Capital One, Goldman Sachs, ING, LinkedIn, Netflix, Pinterest, Rabobank,
> Target, The New York Times, Uber, Yelp, and Zalando, among others.
>
> A big thank you for the following 26 contributors to this release!
>
> A. Sophie Blee-Goldman, Andy Wilkinson, Bob Barrett, Bruno Cadonna,
> Chia-Ping Tsai, Chris Egerton, dengziming, Greg Harris, Ismael Juma, Jim
> Galasyn, John Roesler, Julien Jean Paul Sirocchi, Lee Dongjin, Luke Chen,
> Manikumar Reddy, Matthias J. Sax, Michael G. Noll, Mickael Maison, Rajini
> Sivaram, Ramesh Krishnan M, Randall Hauch, Sharath Bhat, Stanislav
> Vodetskyi, Walker Carlson, Yilong Chang
>
> We welcome your help and feedback. For more information on how to
> report problems, and to get involved, visit the project website at
> https://kafka.apache.org/
>
> Thank you!
>
>
> Cheers,
>
> Sophie
>

[ANNOUNCE] Apache Kafka 2.6.2

[Sophie Blee-Goldman]

The Apache Kafka community is pleased to announce the release for Apache
Kafka 2.6.2

This is a bug fix release and it includes fixes and improvements from
35 JIRAs, including a few critical bugs.

All of the changes in this release can be found in the release notes:
https://www.apache.org/dist/kafka/2.6.2/RELEASE_NOTES.html


You can download the source and binary release (Scala 2.12
and 2.13) from:
https://kafka.apache.org/downloads#2.6.2

---


Apache Kafka is a distributed streaming platform with four core APIs:


** The Producer API allows an application to publish a stream of records to
one or more Kafka topics.

** The Consumer API allows an application to subscribe to one or more
topics and process the stream of records produced to them.

** The Streams API allows an application to act as a stream processor,
consuming an input stream from one or more topics and producing an
output stream to one or more output topics, effectively transforming the
input streams to output streams.

** The Connector API allows building and running reusable producers or
consumers that connect Kafka topics to existing applications or data
systems. For example, a connector to a relational database might
capture every change to a table.


With these APIs, Kafka can be used for two broad classes of application:

** Building real-time streaming data pipelines that reliably get data
between systems or applications.

** Building real-time streaming applications that transform or react
to the streams of data.


Apache Kafka is in use at large and small companies worldwide, including
Capital One, Goldman Sachs, ING, LinkedIn, Netflix, Pinterest, Rabobank,
Target, The New York Times, Uber, Yelp, and Zalando, among others.

A big thank you for the following 26 contributors to this release!

A. Sophie Blee-Goldman, Andy Wilkinson, Bob Barrett, Bruno Cadonna,
Chia-Ping Tsai, Chris Egerton, dengziming, Greg Harris, Ismael Juma, Jim
Galasyn, John Roesler, Julien Jean Paul Sirocchi, Lee Dongjin, Luke Chen,
Manikumar Reddy, Matthias J. Sax, Michael G. Noll, Mickael Maison, Rajini
Sivaram, Ramesh Krishnan M, Randall Hauch, Sharath Bhat, Stanislav
Vodetskyi, Walker Carlson, Yilong Chang

We welcome your help and feedback. For more information on how to
report problems, and to get involved, visit the project website at
https://kafka.apache.org/

Thank you!


Cheers,

Sophie

[GitHub] [kafka-site] ableegoldman merged pull request #351: Add release info and download links for 2.6.2

[GitBox]

ableegoldman merged pull request #351:
URL: https://github.com/apache/kafka-site/pull/351


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [kafka-site] guozhangwang commented on pull request #352: Fix typo in Streams DSL API

[GitBox]

guozhangwang commented on pull request #352:
URL: https://github.com/apache/kafka-site/pull/352#issuecomment-824230478


   Thanks @edwardkenfox , I found in the kafka repo this is also typoed: 
https://github.com/apache/kafka/blob/trunk/docs/streams/developer-guide/dsl-api.html#L1077
 will go ahead and fix it as well.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [kafka-site] guozhangwang merged pull request #352: Fix typo in Streams DSL API

[GitBox]

guozhangwang merged pull request #352:
URL: https://github.com/apache/kafka-site/pull/352


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

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

[Sarwar Bhuiyan]

Congrats Bill!

On Wed, Apr 21, 2021 at 5:52 PM Mickael Maison 
wrote:

> Congratulations Bill, well deserved!
>
> On Sat, Apr 17, 2021 at 11:26 PM Adam Bellemare
>  wrote:
> >
> > Congratulations Bill!!
> >
> > > On Apr 17, 2021, at 5:20 PM, Kowshik Prakasam 
> > > 
> wrote:
> > >
> > > Congrats Bill!
> > >
> > >
> > > Cheers,
> > > Kowshik
> > >
> > >> On Mon, Apr 12, 2021, 11:15 AM Randall Hauch 
> wrote:
> > >>
> > >> Congratulations, Bill!
> > >>
> > >>> On Mon, Apr 12, 2021 at 11:02 AM Guozhang Wang 
> wrote:
> > >>>
> > >>> Congratulations Bill !
> > >>>
> > >>> Guozhang
> > >>>
> >  On Wed, Apr 7, 2021 at 6:16 PM 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
> > 
> > >>>
> > >>>
> > >>> --
> > >>> -- Guozhang
> > >>>
> > >>
>

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

[Mickael Maison]

Congratulations Bill, well deserved!

On Sat, Apr 17, 2021 at 11:26 PM Adam Bellemare
 wrote:
>
> Congratulations Bill!!
>
> > On Apr 17, 2021, at 5:20 PM, Kowshik Prakasam 
> >  wrote:
> >
> > Congrats Bill!
> >
> >
> > Cheers,
> > Kowshik
> >
> >> On Mon, Apr 12, 2021, 11:15 AM Randall Hauch  wrote:
> >>
> >> Congratulations, Bill!
> >>
> >>> On Mon, Apr 12, 2021 at 11:02 AM Guozhang Wang  wrote:
> >>>
> >>> Congratulations Bill !
> >>>
> >>> Guozhang
> >>>
>  On Wed, Apr 7, 2021 at 6:16 PM 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
> 
> >>>
> >>>
> >>> --
> >>> -- Guozhang
> >>>
> >>

Re: [VOTE] 2.7.1 RC2

[Mickael Maison]

Bumping this thread

Can we get a few more votes?

Thanks


On Thu, Apr 15, 2021 at 5:37 PM Bill Bejeck  wrote:
>
> Mickael,
>
> Thanks for running the release.
>
> I validated the checksums and signatures, built the project from src, and
> ran the unit tests.
> I'm +1(binding).
>
> -Bill
>
> On Wed, Apr 14, 2021 at 7:31 PM John Roesler  wrote:
>
> > Hi Mickael,
> >
> > I verified the signatures and checksums, ran the tests, and
> > spot-checked the license.
> >
> > I'm +1 (binding).
> >
> > Thanks for driving this release!
> > -John
> >
> > On Fri, 2021-04-09 at 11:07 +0100, Mickael Maison wrote:
> > > Hi,
> > >
> > > Here is a successful build of 2.7.1 RC2:
> > > https://ci-builds.apache.org/job/Kafka/job/kafka-2.7-jdk8/144/
> > >
> > > Thanks
> > >
> > > On Thu, Apr 8, 2021 at 6:27 PM Mickael Maison 
> > wrote:
> > > >
> > > > Hello Kafka users, developers and client-developers,
> > > >
> > > > This is the third candidate for release of Apache Kafka 2.7.1.
> > > >
> > > > Since 2.7.1 RC1, the following JIRAs have been fixed: KAFKA-12593,
> > > > KAFKA-12474, KAFKA-12602.
> > > >
> > > > Release notes for the 2.7.1 release:
> > > > https://home.apache.org/~mimaison/kafka-2.7.1-rc2/RELEASE_NOTES.html
> > > >
> > > > *** Please download, test and vote by Friday, April 16, 5pm BST
> > > >
> > > > 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/~mimaison/kafka-2.7.1-rc2/
> > > >
> > > > * Maven artifacts to be voted upon:
> > > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > > >
> > > > * Javadoc:
> > > > https://home.apache.org/~mimaison/kafka-2.7.1-rc2/javadoc/
> > > >
> > > > * Tag to be voted upon (off 2.7 branch) is the 2.7.1 tag:
> > > > https://github.com/apache/kafka/releases/tag/2.7.1-rc2
> > > >
> > > > * Documentation:
> > > > https://kafka.apache.org/27/documentation.html
> > > >
> > > > * Protocol:
> > > > https://kafka.apache.org/27/protocol.html
> > > >
> > > > * Successful Jenkins builds for the 2.7 branch:
> > > > The build is still running, I'll update the thread once it's complete
> > > >
> > > > /**
> > > >
> > > > Thanks,
> > > > Mickael
> >
> >
> >

Re: [Go] Flight client app metadata access

[Paul Whalen]

Whoops, please ignore.  I didn't pay enough attention to my autocomplete
for Apache mailing lists :)

On Wed, Apr 21, 2021 at 11:37 AM Paul Whalen  wrote:

> Hi all,
>
> I'm using the Go Flight client, working off of this example:
> https://github.com/apache/arrow/blob/master/go/arrow/flight/flight_test.go
>
> I've found that there isn't a very convenient way to access the app
> metadata from a Flight stream, because the ipc.Reader you get from calling
> flight.NewRecordReader() only exposes the array.Record as you read data
> from it.  This makes sense to me because only Flight defines the App
> Metadata concept, not the Arrow IPC format on its own.  I've been able to
> work around it by dropping down a level, and building an alternate
> flight.dataMessageReader but this seems subpar.
>
> Am I missing something?  Or is there an opportunity to make the result of
> flight.NewRecordReader() a bit more useful such that it includes the app
> metadata?  Perhaps a type more specific to Flight, not just IPC in
> general.  On the Java side I see that FlightStream has getLatestMetadata()
> which seems like a pattern worth following.
>
> Thanks,
> Paul
>

[jira] [Created] (KAFKA-12704) Concurrent calls to AbstractHerder::getConnector can potentially create two connector instances

[Kalpesh Patel (Jira)]

Kalpesh Patel created KAFKA-12704:
-

 Summary: Concurrent calls to AbstractHerder::getConnector can 
potentially create two connector instances
 Key: KAFKA-12704
 URL: https://issues.apache.org/jira/browse/KAFKA-12704
 Project: Kafka
  Issue Type: Bug
  Components: KafkaConnect
Reporter: Kalpesh Patel


Requests to the {{PUT /connector-plugins/\{connectorType}/config/validate}} 
endpoint are [delegated to the 
herder|https://github.com/apache/kafka/blob/16ee326755e3f13914a0ed446c34c84e65fc0bc4/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/rest/resources/ConnectorPluginsResource.java#L81],
 which [caches connector 
instances|https://github.com/apache/kafka/blob/16ee326755e3f13914a0ed446c34c84e65fc0bc4/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/AbstractHerder.java#L536-L544]
 that are used [during config 
validation|https://github.com/apache/kafka/blob/16ee326755e3f13914a0ed446c34c84e65fc0bc4/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/AbstractHerder.java#L310].
 This has the effect that, should concurrent requests to that endpoint occur 
for the same connector type, the same connector instance may be responsible for 
[validating those 
configurations|https://github.com/apache/kafka/blob/16ee326755e3f13914a0ed446c34c84e65fc0bc4/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/AbstractHerder.java#L334]
 concurrently _(may_ instead of _will_ because there is also a race condition 
in the {{AbstractHerder::getConnector}} method that potentially fails to detect 
that an instance of the connector has already been created and, as a result, 
creates a second instance).

This is slightly problematic because the 
[Connector::validate|https://github.com/apache/kafka/blob/16ee326755e3f13914a0ed446c34c84e65fc0bc4/connect/api/src/main/java/org/apache/kafka/connect/connector/Connector.java#L122-L127]
 method is not marked as thread-safe. However, because a lot of connectors out 
there tend to use the default implementation for that method, it's probably not 
super urgent that we patch this immediately.

A couple of options are:
 # Update the docs for that method to specify that it must be thread-safe
 # Rewrite the connector validation logic in the framework to avoid 
concurrently invoking {{Connector::validate}} on the same instance.



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

[Go] Flight client app metadata access

[Paul Whalen]

Hi all,

I'm using the Go Flight client, working off of this example:
https://github.com/apache/arrow/blob/master/go/arrow/flight/flight_test.go

I've found that there isn't a very convenient way to access the app
metadata from a Flight stream, because the ipc.Reader you get from calling
flight.NewRecordReader() only exposes the array.Record as you read data
from it.  This makes sense to me because only Flight defines the App
Metadata concept, not the Arrow IPC format on its own.  I've been able to
work around it by dropping down a level, and building an alternate
flight.dataMessageReader but this seems subpar.

Am I missing something?  Or is there an opportunity to make the result of
flight.NewRecordReader() a bit more useful such that it includes the app
metadata?  Perhaps a type more specific to Flight, not just IPC in
general.  On the Java side I see that FlightStream has getLatestMetadata()
which seems like a pattern worth following.

Thanks,
Paul

[GitHub] [kafka-site] rhauch commented on a change in pull request #351: Add release info and download links for 2.6.2

[GitBox]

rhauch commented on a change in pull request #351:
URL: https://github.com/apache/kafka-site/pull/351#discussion_r617627573



##
File path: 26/generated/connect_config.html
##
@@ -375,7 +375,7 @@ admin.listeners
 
 Type:list
 Default:null
-Valid 
Values:org.apache.kafka.connect.runtime.WorkerConfig$AdminListenersValidator@7b3300e5
+Valid 
Values:org.apache.kafka.connect.runtime.WorkerConfig$AdminListenersValidator@d2cc05a

Review comment:
   Thanks for dealing with this. Looks like a community member already 
submitted a PR, so we'll fix that shortly.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Resolved] (KAFKA-12680) Failed to restart the broker in kraft mode

[Wenbing Shen (Jira)]

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

Wenbing Shen resolved KAFKA-12680.
--
Resolution: Not A Problem

> Failed to restart the broker in kraft mode
> --
>
> Key: KAFKA-12680
> URL: https://issues.apache.org/jira/browse/KAFKA-12680
> Project: Kafka
>  Issue Type: Bug
>Reporter: Wenbing Shen
>Priority: Major
>
> I tested kraft mode for the first time today, I deployed a single node kraft 
> mode broker according to the documentation:
> [https://github.com/apache/kafka/blob/6d1d68617ecd023b787f54aafc24a4232663428d/config/kraft/README.md]
>  
> first step: ./bin/kafka-storage.sh random-uuid
> Second step: Use the uuid generated above to execute the following commands:
> ./bin/kafka-storage.sh format -t  -c ./config/kraft/server.properties
>  
> third step: ./bin/kafka-server-start.sh ./config/kraft/server.properties
>  
> Then I created two topics with two partitions and a single replica.
> ./bin/kafka-topics.sh --create --topic test-01 --partitions 2 
> --replication-factor 1 --bootstrap-server localhost:9092
> Verify that there is no problem with production and consumption, but when I 
> call kafka-server-stop.sh, when I call the start command again, the broker 
> starts to report an error.
> I am not sure if it is a known bug or a problem with my usage
>  
> [2021-04-18 00:19:37,443] ERROR Exiting Kafka due to fatal exception 
> (kafka.Kafka$)
> java.io.IOException: Invalid argument
>  at java.io.RandomAccessFile.setLength(Native Method)
>  at kafka.log.AbstractIndex.$anonfun$resize$1(AbstractIndex.scala:189)
>  at kafka.log.AbstractIndex.resize(AbstractIndex.scala:175)
>  at 
> kafka.log.AbstractIndex.$anonfun$trimToValidSize$1(AbstractIndex.scala:241)
>  at kafka.log.AbstractIndex.trimToValidSize(AbstractIndex.scala:241)
>  at kafka.log.LogSegment.recover(LogSegment.scala:385)
>  at kafka.log.Log.recoverSegment(Log.scala:741)
>  at kafka.log.Log.recoverLog(Log.scala:894)
>  at kafka.log.Log.$anonfun$loadSegments$2(Log.scala:816)
>  at kafka.log.Log$$Lambda$153/391630194.apply$mcJ$sp(Unknown Source)
>  at scala.runtime.java8.JFunction0$mcJ$sp.apply(JFunction0$mcJ$sp.scala:17)
>  at kafka.log.Log.retryOnOffsetOverflow(Log.scala:2456)
>  at kafka.log.Log.loadSegments(Log.scala:816)
>  at kafka.log.Log.(Log.scala:326)
>  at kafka.log.Log$.apply(Log.scala:2593)
>  at kafka.raft.KafkaMetadataLog$.apply(KafkaMetadataLog.scala:358)
>  at kafka.raft.KafkaRaftManager.buildMetadataLog(RaftManager.scala:253)
>  at kafka.raft.KafkaRaftManager.(RaftManager.scala:127)
>  at kafka.server.KafkaRaftServer.(KafkaRaftServer.scala:74)
>  at kafka.Kafka$.buildServer(Kafka.scala:79)
>  at kafka.Kafka$.main(Kafka.scala:87)
>  at kafka.Kafka.main(Kafka.scala)



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

[jira] [Reopened] (KAFKA-12680) Failed to restart the broker in kraft mode

[Wenbing Shen (Jira)]

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

Wenbing Shen reopened KAFKA-12680:
--

> Failed to restart the broker in kraft mode
> --
>
> Key: KAFKA-12680
> URL: https://issues.apache.org/jira/browse/KAFKA-12680
> Project: Kafka
>  Issue Type: Bug
>Reporter: Wenbing Shen
>Priority: Major
>
> I tested kraft mode for the first time today, I deployed a single node kraft 
> mode broker according to the documentation:
> [https://github.com/apache/kafka/blob/6d1d68617ecd023b787f54aafc24a4232663428d/config/kraft/README.md]
>  
> first step: ./bin/kafka-storage.sh random-uuid
> Second step: Use the uuid generated above to execute the following commands:
> ./bin/kafka-storage.sh format -t  -c ./config/kraft/server.properties
>  
> third step: ./bin/kafka-server-start.sh ./config/kraft/server.properties
>  
> Then I created two topics with two partitions and a single replica.
> ./bin/kafka-topics.sh --create --topic test-01 --partitions 2 
> --replication-factor 1 --bootstrap-server localhost:9092
> Verify that there is no problem with production and consumption, but when I 
> call kafka-server-stop.sh, when I call the start command again, the broker 
> starts to report an error.
> I am not sure if it is a known bug or a problem with my usage
>  
> [2021-04-18 00:19:37,443] ERROR Exiting Kafka due to fatal exception 
> (kafka.Kafka$)
> java.io.IOException: Invalid argument
>  at java.io.RandomAccessFile.setLength(Native Method)
>  at kafka.log.AbstractIndex.$anonfun$resize$1(AbstractIndex.scala:189)
>  at kafka.log.AbstractIndex.resize(AbstractIndex.scala:175)
>  at 
> kafka.log.AbstractIndex.$anonfun$trimToValidSize$1(AbstractIndex.scala:241)
>  at kafka.log.AbstractIndex.trimToValidSize(AbstractIndex.scala:241)
>  at kafka.log.LogSegment.recover(LogSegment.scala:385)
>  at kafka.log.Log.recoverSegment(Log.scala:741)
>  at kafka.log.Log.recoverLog(Log.scala:894)
>  at kafka.log.Log.$anonfun$loadSegments$2(Log.scala:816)
>  at kafka.log.Log$$Lambda$153/391630194.apply$mcJ$sp(Unknown Source)
>  at scala.runtime.java8.JFunction0$mcJ$sp.apply(JFunction0$mcJ$sp.scala:17)
>  at kafka.log.Log.retryOnOffsetOverflow(Log.scala:2456)
>  at kafka.log.Log.loadSegments(Log.scala:816)
>  at kafka.log.Log.(Log.scala:326)
>  at kafka.log.Log$.apply(Log.scala:2593)
>  at kafka.raft.KafkaMetadataLog$.apply(KafkaMetadataLog.scala:358)
>  at kafka.raft.KafkaRaftManager.buildMetadataLog(RaftManager.scala:253)
>  at kafka.raft.KafkaRaftManager.(RaftManager.scala:127)
>  at kafka.server.KafkaRaftServer.(KafkaRaftServer.scala:74)
>  at kafka.Kafka$.buildServer(Kafka.scala:79)
>  at kafka.Kafka$.main(Kafka.scala:87)
>  at kafka.Kafka.main(Kafka.scala)



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

[jira] [Created] (KAFKA-12703) Unencrypted PEM files don't work

[Brian Bascoy (Jira)]

Brian Bascoy created KAFKA-12703:


 Summary: Unencrypted PEM files don't work
 Key: KAFKA-12703
 URL: https://issues.apache.org/jira/browse/KAFKA-12703
 Project: Kafka
  Issue Type: Bug
  Components: clients
Affects Versions: 2.8.0
Reporter: Brian Bascoy


Unencrypted PEM files seem to be internally [supported in the 
codebase|https://github.com/apache/kafka/blob/a46beb9d29781e0709baf596601122f770a5fa31/clients/src/main/java/org/apache/kafka/common/security/ssl/DefaultSslEngineFactory.java#L509]
 but setting an ssl.key.password is currently enforced by createKeystore (on 
DefaultSslEngineFactory). I was unable to find a reason for this, so I wonder 
if this limitation could simply be removed:
 [https://github.com/pera/kafka/commit/8df2feab5fc6955cf8c89a7d132f05d8f562e16b]

 

Thanks



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

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

[Apache Jenkins Server]

See 

[jira] [Resolved] (KAFKA-12680) Failed to restart the broker in kraft mode

[Wenbing Shen (Jira)]

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

Wenbing Shen resolved KAFKA-12680.
--
Resolution: Cannot Reproduce

> Failed to restart the broker in kraft mode
> --
>
> Key: KAFKA-12680
> URL: https://issues.apache.org/jira/browse/KAFKA-12680
> Project: Kafka
>  Issue Type: Bug
>Reporter: Wenbing Shen
>Priority: Major
>
> I tested kraft mode for the first time today, I deployed a single node kraft 
> mode broker according to the documentation:
> [https://github.com/apache/kafka/blob/6d1d68617ecd023b787f54aafc24a4232663428d/config/kraft/README.md]
>  
> first step: ./bin/kafka-storage.sh random-uuid
> Second step: Use the uuid generated above to execute the following commands:
> ./bin/kafka-storage.sh format -t  -c ./config/kraft/server.properties
>  
> third step: ./bin/kafka-server-start.sh ./config/kraft/server.properties
>  
> Then I created two topics with two partitions and a single replica.
> ./bin/kafka-topics.sh --create --topic test-01 --partitions 2 
> --replication-factor 1 --bootstrap-server localhost:9092
> Verify that there is no problem with production and consumption, but when I 
> call kafka-server-stop.sh, when I call the start command again, the broker 
> starts to report an error.
> I am not sure if it is a known bug or a problem with my usage
>  
> [2021-04-18 00:19:37,443] ERROR Exiting Kafka due to fatal exception 
> (kafka.Kafka$)
> java.io.IOException: Invalid argument
>  at java.io.RandomAccessFile.setLength(Native Method)
>  at kafka.log.AbstractIndex.$anonfun$resize$1(AbstractIndex.scala:189)
>  at kafka.log.AbstractIndex.resize(AbstractIndex.scala:175)
>  at 
> kafka.log.AbstractIndex.$anonfun$trimToValidSize$1(AbstractIndex.scala:241)
>  at kafka.log.AbstractIndex.trimToValidSize(AbstractIndex.scala:241)
>  at kafka.log.LogSegment.recover(LogSegment.scala:385)
>  at kafka.log.Log.recoverSegment(Log.scala:741)
>  at kafka.log.Log.recoverLog(Log.scala:894)
>  at kafka.log.Log.$anonfun$loadSegments$2(Log.scala:816)
>  at kafka.log.Log$$Lambda$153/391630194.apply$mcJ$sp(Unknown Source)
>  at scala.runtime.java8.JFunction0$mcJ$sp.apply(JFunction0$mcJ$sp.scala:17)
>  at kafka.log.Log.retryOnOffsetOverflow(Log.scala:2456)
>  at kafka.log.Log.loadSegments(Log.scala:816)
>  at kafka.log.Log.(Log.scala:326)
>  at kafka.log.Log$.apply(Log.scala:2593)
>  at kafka.raft.KafkaMetadataLog$.apply(KafkaMetadataLog.scala:358)
>  at kafka.raft.KafkaRaftManager.buildMetadataLog(RaftManager.scala:253)
>  at kafka.raft.KafkaRaftManager.(RaftManager.scala:127)
>  at kafka.server.KafkaRaftServer.(KafkaRaftServer.scala:74)
>  at kafka.Kafka$.buildServer(Kafka.scala:79)
>  at kafka.Kafka$.main(Kafka.scala:87)
>  at kafka.Kafka.main(Kafka.scala)



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

[jira] [Created] (KAFKA-12702) Unhandled exception caught in InterBrokerSendThread

[Wenbing Shen (Jira)]

Wenbing Shen created KAFKA-12702:


 Summary: Unhandled exception caught in InterBrokerSendThread
 Key: KAFKA-12702
 URL: https://issues.apache.org/jira/browse/KAFKA-12702
 Project: Kafka
  Issue Type: Bug
Affects Versions: 2.8.0
Reporter: Wenbing Shen
 Attachments: afterFixing.png, beforeFixing.png

In kraft mode, if listeners and advertised.listeners are not configured with 
host addresses, the host parameter value of Listener in 
BrokerRegistrationRequestData will be null. When the broker is started, a null 
pointer exception will be thrown, causing startup failure.

A feasible solution is to replace the empty host of endPoint in 
advertisedListeners with InetAddress.getLocalHost.getCanonicalHostName in 
Broker Server when building networkListeners.

The following is the debug log:

before fixing:

[2021-04-21 14:15:20,032] DEBUG (broker-2-to-controller-send-thread 
org.apache.kafka.clients.NetworkClient 522) [broker-2-to-controller] Sending 
BROKER_REGISTRATION request with header RequestHeader(apiKey=BROKER_REGIS
TRATION, apiVersion=0, clientId=2, correlationId=6) and timeout 3 to node 
2: BrokerRegistrationRequestData(brokerId=2, 
clusterId='nCqve6D1TEef3NpQniA0Mg', incarnationId=X8w4_1DFT2yUjOm6asPjIQ, 
listeners=[Listener(n
ame='PLAINTEXT', {color:#FF}host=null,{color} port=9092, 
securityProtocol=0)], features=[], rack=null)
[2021-04-21 14:15:20,033] ERROR (broker-2-to-controller-send-thread 
kafka.server.BrokerToControllerRequestThread 76) 
[broker-2-to-controller-send-thread]: unhandled exception caught in 
InterBrokerSendThread
java.lang.NullPointerException
 at 
org.apache.kafka.common.message.BrokerRegistrationRequestData$Listener.addSize(BrokerRegistrationRequestData.java:515)
 at 
org.apache.kafka.common.message.BrokerRegistrationRequestData.addSize(BrokerRegistrationRequestData.java:216)
 at org.apache.kafka.common.protocol.SendBuilder.buildSend(SendBuilder.java:218)
 at 
org.apache.kafka.common.protocol.SendBuilder.buildRequestSend(SendBuilder.java:187)
 at 
org.apache.kafka.common.requests.AbstractRequest.toSend(AbstractRequest.java:101)
 at org.apache.kafka.clients.NetworkClient.doSend(NetworkClient.java:525)
 at org.apache.kafka.clients.NetworkClient.doSend(NetworkClient.java:501)
 at org.apache.kafka.clients.NetworkClient.send(NetworkClient.java:461)
 at 
kafka.common.InterBrokerSendThread.$anonfun$sendRequests$1(InterBrokerSendThread.scala:104)
 at 
kafka.common.InterBrokerSendThread.$anonfun$sendRequests$1$adapted(InterBrokerSendThread.scala:99)
 at kafka.common.InterBrokerSendThread$$Lambda$259/910445654.apply(Unknown 
Source)
 at scala.collection.IterableOnceOps.foreach(IterableOnce.scala:563)
 at scala.collection.IterableOnceOps.foreach$(IterableOnce.scala:561)
 at scala.collection.AbstractIterable.foreach(Iterable.scala:919)
 at 
kafka.common.InterBrokerSendThread.sendRequests(InterBrokerSendThread.scala:99)
 at kafka.common.InterBrokerSendThread.pollOnce(InterBrokerSendThread.scala:73)
 at 
kafka.server.BrokerToControllerRequestThread.doWork(BrokerToControllerChannelManager.scala:368)
 at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:96)
[2021-04-21 14:15:20,034] INFO (broker-2-to-controller-send-thread 
kafka.server.BrokerToControllerRequestThread 66) 
[broker-2-to-controller-send-thread]: Stopped



after fixing:

[2021-04-21 15:05:01,095] DEBUG (BrokerToControllerChannelManager broker=2 
name=heartbeat org.apache.kafka.clients.NetworkClient 512) 
[BrokerToControllerChannelManager broker=2 name=heartbeat] Sending 
BROKER_REGISTRATI
ON request with header RequestHeader(apiKey=BROKER_REGISTRATION, apiVersion=0, 
clientId=2, correlationId=0) and timeout 3 to node 2: 
BrokerRegistrationRequestData(brokerId=2, clusterId='nCqve6D1TEef3NpQniA0Mg', 
inc
arnationId=xF29h_IRR1KzrERWwssQ2w, listeners=[Listener(name='PLAINTEXT', 
host='hdpxxx.cn', port=9092, securityProtocol=0)], features=[], rack=null)

 

 



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