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: txHandler and txSync do not start after node catching up #4775

Closed
algonautshant opened this issue Nov 9, 2022 · 0 comments
Closed

Bug: txHandler and txSync do not start after node catching up #4775

algonautshant opened this issue Nov 9, 2022 · 0 comments
Assignees
Labels
bug Something isn't working Team Carbon-11

Comments

@algonautshant
Copy link
Contributor

algonautshant commented Nov 9, 2022

The txHandler and txSyncer are stopped when catching up from a catchpoint, and start again afterwards.

But they never really start. The main loop of these services rely on a context to stop. That context is canceled when stopping. Then, when the services are started again, the contexts remain canceled, which leads for the service to immediately end.

The fix is to create a new context when starting these services.

txSync has another control mechanism to wait starting the loop, which should be handled for "re"-start.

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

No branches or pull requests

2 participants