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

Gossipsub: unable to re-publish message after failed attempts. #1926

Closed
xu-cheng opened this issue Jan 15, 2021 · 3 comments
Closed

Gossipsub: unable to re-publish message after failed attempts. #1926

xu-cheng opened this issue Jan 15, 2021 · 3 comments

Comments

@xu-cheng
Copy link
Contributor

Sometimes, publishing message may fail in Gossipsub due to PublishError::InsufficientPeers. In this case, the application may want to retry the publish later. However, the subsequent re-publish would fail due to PublishError::Duplicate when a content-based hash is used to compute message id.

I think if a message fails to be published, it should be removed from duplicate_cache also maybe mcache.

@mxinden
Copy link
Member

mxinden commented Jan 18, 2021

@AgeManning @blacktemplar would you mind taking a look?

@AgeManning
Copy link
Contributor

Thanks for raising this edge case.

This is an issue with content-addressed messages. I've updated the gossipsub protocol in #1930 to only add messages to the caches if they have been sent to at least one peer.

@romanb
Copy link
Contributor

romanb commented Jan 20, 2021

Closed by #1930.

@romanb romanb closed this as completed Jan 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants