Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: Send Queue full #177

Open
erhant opened this issue Feb 3, 2025 · 1 comment
Open

bug: Send Queue full #177

erhant opened this issue Feb 3, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@erhant
Copy link
Member

erhant commented Feb 3, 2025

With v0.3 we have moved to latest branch of libp2p, instead of our fork which was out-dated.

[WARN  libp2p_gossipsub::behaviour] Send Queue full. Could not send IDontWant(IDontWant { message_ids: [MessageId(d70001e518f515ee)] }).

This happens when we do pongs in compute node.

@erhant erhant added the bug Something isn't working label Feb 3, 2025
@erhant
Copy link
Member Author

erhant commented Feb 3, 2025

  1. behaviour.rs#L2841 is where we get the Send Queue full. ... message.
  2. rpc.rs#L82 the error is returned here due to len >= self.priority_cap check
  3. rpc.rs#L49 priority_cap: cap / 2 is set here
  4. Sender::new is alays called with self.config.connection_handler_queue_len() (see behaviour.rs#L3119 and [behaviour.rs#L3092
  5. connection_handler_queue_len is given via config builder function connection_handler_queue_len so it is directly related to this error

Giving a larger value for this increases the memory usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant