linkedin / linkedin/Burrow

Compatibility with kafka version 0.11.0.

Open
#766 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
4k
Forks
818
Avg merge
1h 14m
Merged PRs (30d)
1

Description

I'm using kafka version 0.11.0.0, and I'm getting the following log on the broker:

I used the two kafka images to test:

- confluentinc/cp-kafka:3.3.3 [Release Notes](https://docs.confluent.io/3.3.3/release-notes.html#)
- wurstmeister/kafka:0.11.0.0

My configurations burrow.toml:

```
[zookeeper]
servers=[ "zookeeper:2181" ]
timeout=6
root-path="/burrow"

[client-profile.profile]
kafka-version="0.11.0"
client-id="docker-client"

[cluster.local]
client-profile="profile"
class-name="kafka"
servers=[ "kafka:9092" ]
topic-refresh=60
offset-refresh=30
groups-reaper-refresh=30

[consumer.local]
class-name="kafka"
cluster="local"
servers=[ "kafka:9092" ]

[consumer.local_zk]
class-name="kafka_zk"
cluster="local"
servers=[ "zookeeper:2181" ]
zookeeper-path="/local"
zookeeper-timeout=30
group-denylist="^(console-consumer-|python-kafka-consumer-).*$"
group-allowlist=""

[httpserver.default]
address=":8000"
```

Error show:

> [2022-11-16 14:16:29,591] ERROR Closing socket for 192.168.0.2:9092-192.168.0.4:41204 because of error (kafka.network.Processor)
> org.apache.kafka.common.errors.InvalidRequestException: Error getting request for apiKey: 3 and apiVersion: 5
> Caused by: java.lang.IllegalArgumentException: Invalid version for API key METADATA: 5
> at org.apache.kafka.common.protocol.ApiKeys.schemaFor(ApiKeys.java:173)
> at org.apache.kafka.common.protocol.ApiKeys.requestSchema(ApiKeys.java:141)
> at org.apache.kafka.common.protocol.ApiKeys.parseRequest(ApiKeys.java:149)
> at org.apache.kafka.common.requests.AbstractRequest.getRequest(AbstractRequest.java:112)
> at kafka.network.RequestChannel$Request.liftedTree2$1(RequestChannel.scala:99)
> at kafka.network.RequestChannel$Request.(RequestChannel.scala:93)
> at kafka.network.Processor.$anonfun$processCompletedReceives$1(SocketServer.scala:519)
> at kafka.network.Processor.$anonfun$processCompletedReceives$1$adapted(SocketServer.scala:510)
> at scala.collection.Iterator.foreach(Iterator.scala:929)
> at scala.collection.Iterator.foreach$(Iterator.scala:929)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1417)
> at scala.collection.IterableLike.foreach(IterableLike.scala:71)
> at scala.collection.IterableLike.foreach$(IterableLike.scala:70)
> at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
> at kafka.network.Processor.processCompletedReceives(SocketServer.scala:510)
> at kafka.network.Processor.run(SocketServer.scala:436)
> at java.lang.Thread.run(Thread.java:748)




Am I forgetting to do some configuration or is it indeed a problem?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report centers on Burrow's Kafka client profile in burrow.toml and Kafka METADATA apiKey 3/version 5 requests. Reproduce with confluentinc/cp-kafka:3.3.3 and wurstmeister/kafka:0.11.0.0 using the supplied configuration, then trace the Kafka version handling; done means establishing whether 0.11.0 compatibility works or documenting the limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kafka
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.