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

Understand the number of messages dropped due to RouteBackNotFound #3688

Open
bowenwang1996 opened this issue Dec 3, 2020 · 3 comments
Open
Labels
A-network Area: Network

Comments

@bowenwang1996
Copy link
Collaborator

We often see, in both single-sharded network and multi-sharded network, that some messages get dropped because its route back cannot be found. We should first understand the number of the dropped messages and then decide how to proceed. There is a PR #3088 that should address the issue mostly, but it may take some time to finish and we may need to revive it if a significant amount of messages are lost due to the route back issue.

@bowenwang1996 bowenwang1996 added the A-chain Area: Chain, client & related label Dec 3, 2020
@bowenwang1996 bowenwang1996 added A-network Area: Network and removed A-chain Area: Chain, client & related labels Jun 29, 2021
@stale
Copy link

stale bot commented Sep 27, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale
Copy link

stale bot commented Dec 27, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Dec 27, 2021
@pmnoxx pmnoxx removed their assignment Mar 7, 2022
@stale
Copy link

stale bot commented Jun 5, 2022

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Jun 5, 2022
@akhi3030 akhi3030 removed the S-stale label Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-network Area: Network
Projects
None yet
Development

No branches or pull requests

4 participants