This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 138
[BUG]Error parsing request header. Our best guess of the apiKey is: 116 #145
Labels
Comments
@jiazhai Can you help with this question? |
@yuanweikang2020 which version is are you using? |
我切换了指定版本,但是还是出错了,pulsar错误信息:
|
@yuanweikang2020 This looks like the package not loaded well. Is the kop.nar placed well under dir: share/java/pulsar/potocols? Is there any other error logs in the broker side? |
@yuanweikang2020 any updates about Jia's last comment? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
我在Pulsar上配置KoP之后,使用Golang
Shopify/sarama
Kafka客户端进行生产消息时出错,Pulsar错误信息:Error parsing request header. Our best guess of the apiKey is: 116
;sarama
Kafka客户端错误信息:"kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"
To Reproduce
Steps to reproduce the behavior:
我运行我的程序,然后出错:
unable to create kafka producer: "kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"
我尝试修改了
config.Version
参数为sarama.V2_0_1_0
,sarama.V2_0_0_0
,sarama.V2_1_0_0
都是同样的错误3. 我在运行我的生产程序时,Pulsar出错了,错误信息:
Error parsing request header. Our best guess of the apiKey is: 116
Expected behavior
想请问一下,怎样可以解决。
Screenshots
这个是Pulsar详细错误信息
Additional context
The text was updated successfully, but these errors were encountered: