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

Closed channels should reconnect, rather than letting the app die #2

Open
Eagerod opened this issue May 7, 2023 · 0 comments
Open

Comments

@Eagerod
Copy link
Owner

Eagerod commented May 7, 2023

Right now, the consumer + requester flow starts up 1 channel per CPU. As these fail, they don't reconnect, and when the final one fails, the application exits, and with success, at that.

Failed connections should be re-established, and the app should live indefinitely, rather than relying on passive failure mechanics.

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

1 participant