libp2p / libp2p/go-libp2p-pubsub
When publishing a lot of messages I get "dropping message to peer" log info
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 364
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
Hello
I am trying to send around 50000 - 100000 messages from peer 1 to peer 2, each message is around 300 bytes as fast as libp2p's stack can handle (no time.sleep between each send) and sometimes I get
```
INFO pubsub: dropping message to peer : queue full gossipsub.go:348
```
and sometimes I get:
```
pubsub: Can't deliver message to subscription for topic tx; subscriber too slow pubsub.go:493
```
Since there is no feedback when the message has been sent (or not) in my publish loop I do not know how much I have to wait till the next publish. Is there a good practice advice to accomplish this task?
Thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the queue-full path in gossipsub.go:348 and the slow-subscriber path in pubsub.go:493, then review how the publish loop reports delivery. Determine whether the requested feedback or backpressure behavior is defined by the existing implementation; done would require an agreed approach for safely publishing large message bursts without silent drops.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100