apache / apache/pulsar-client-go
the problem of partition producer number
- Dominant language
- Go
- Stars
- 745
- Forks
- 389
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 3
Description
#### 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
Contributor guide
Research direction
No source files, tests, or entry points are named. Reproduce the broker A bundle unload and broker B load with Pulsar 2.6.0 and Go client 0.1.0, then compare the Go client warnings with the Grafana producer count; done means the producer count remains correct after reconnection and unexpected send receipts do not accumulate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100