Add backend monitoring process #392
Assignees
Comments
code-asher
added a commit
that referenced
this issue
May 5, 2024
This implements connecting at a lower level, giving us a place to respawn the backend and reconnect when it goes down, replacing fullDeployCycle since it does not do that for us. Closes #392.
code-asher
added a commit
that referenced
this issue
May 5, 2024
This implements connecting at a lower level, giving us a place to respawn the backend and reconnect when it goes down, replacing fullDeployCycle since it does not do that for us. Closes #392.
code-asher
added a commit
that referenced
this issue
May 5, 2024
This implements connecting at a lower level, giving us a place to respawn the backend and reconnect when it goes down, replacing fullDeployCycle since it does not do that for us. Closes #392.
|
Kira to test before we release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the backend dies, restart it.
Should tie it to the lifetime of the client, so when the user starts the client we start monitoring, when they close the client we stop monitoring. I think we can just use
clientLifetimefor this, but need to test to be sure.Not 100% sure how to monitor the backend, from what I recall the remote worker has some commands for getting a backend's status, so hopefully it is straightforward.
Essentially this will be an SSH command that runs at an interval, runs the remote worker to check the backend status, and if it is dead it spawns a new one.
The text was updated successfully, but these errors were encountered: