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

Be more resilient against loss of internet connection #7109

Closed
czepluch opened this issue May 31, 2021 · 3 comments
Closed

Be more resilient against loss of internet connection #7109

czepluch opened this issue May 31, 2021 · 3 comments

Comments

@czepluch
Copy link
Contributor

Abstract

If internet connection is lost just briefly on the machine running a Raiden node, the node crashes. This is not an ideal user experience and it makes it harder to guarantee uptime.

Motivation

The user should worry as little as possible about running a Raiden node. If it crashes from just a quick dropped internet connection the user has to worry about running on a very stable connection. Back in the days Raiden handled this more gracefully and the user could even put his laptop to sleep and resume afterwards without the node crashing.

Specification

Allow Raiden to be more graceful when connection is lost instead of crashing the node.

@fredo fredo added this to Mainnet Release Issues in Raiden Berlin Sprint Jun 9, 2021
@fredo fredo moved this from Mainnet Release Issues to Sprint Backlog in Raiden Berlin Sprint Jun 9, 2021
@fredo
Copy link
Contributor

fredo commented Jun 11, 2021

Complex Problem because state machine must stop if one service is not available.

Soft measurements:

  • Add retries to the http requests
  • Send notification what happened
  • restart-on-error flag with potebntial error emssage on next restart.

@fredo
Copy link
Contributor

fredo commented Jun 24, 2021

closed in favor of #7186

@fredo fredo closed this as completed Jun 24, 2021
Raiden Berlin Sprint automation moved this from Sprint Backlog to Done Jun 24, 2021
@ulope
Copy link
Collaborator

ulope commented Jun 28, 2021

One more option we discussed:

  • Add a soft-restart feature that would allow the client to self restart from the outer layer (cli) in case of an exception, removing the need for the user to setup a process manager

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants