the problem of partition producer number

apache / pulsar-client-go

Apache Pulsar Go Client Library

https://pulsar.apache.org/

Apache License 2.0

660 stars 336 forks source link

the problem of partition producer number #327

Open yarthur1 opened 4 years ago

yarthur1 commented 4 years ago

Expected behavior

After a bundle successfully moved from broker A to broker B , goclient log show that partition producer has reconnected new broker, but goclient has lots of warn log like"level=warning msg="Got unexpected send receipt for message: ledgerId:87806 entryId:10433 "...". Grafana dashboard show the number of producer have some change,and eventually is not correct

broker log broker A unload bundle

broker B load bundle

Go client log

grafana

System configuration

Pulsar version: 2.6.0 Go client version: 0.1.0

sijie commented 4 years ago

@yarthur1 I don't think it is a problem on either client or broker side. This sounds like a grafana problem. Have you checked the query to understand if it is a metric problem?

yarthur1 commented 4 years ago

@yarthur1 I don't think it is a problem on either client or broker side. This sounds like a grafana problem. Have you checked the query to understand if it is a metric problem?

But it lead to send rate slow, I have add timeout check on Go client send method to test and find lots of timeout

LvBay commented 4 years ago

@yarthur1 Did you use the same client instance to create both consumers and a producers? I have encountered a similar problem and have submitted a PR to fix it, hope it can help you.

yarthur1 commented 4 years ago

@yarthur1 Did you use the same client instance to create both consumers and a producers? I have encountered a similar problem and have submitted a PR to fix it, hope it can help you.

yes,I use the same client instance. thanks,I will view it