apache / apache/pulsar-client-go
[Bug] Message loss caused by returning msgId -1:-1:x after the server turns on deduplication
Open
- Dominant language
- Go
- Stars
- 745
- Forks
- 389
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 3
Description
```
2025-08-18T10:28:09.779+0800 | DEBUG | [logger/pulsar_log.go:58] Got command! type:SEND_RECEIPT send_receipt:{producer_id:2 sequence_id:63 message_id:{ledgerId:18446744073709551615 entryId:18446744073709551615} highest_sequence_id:18446744073709551615} with payload size: 0 maxMsgSize: 11534336 {"remote_addr": "pulsar://7.34ds79:6650", "local_addr": "7.dsds.43:58326"
```
This message msgId returned -1:-1:x
the server turns on deduplication . version 3.0.4
User feedback on using go coroutines
Occasionally, it occurs, and disabling batch sending does not occur
Contributor guide
Assessment
This issue has not been assessed yet.