-
Notifications
You must be signed in to change notification settings - Fork 638
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
Comments
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
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.
The text was updated successfully, but these errors were encountered: