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

Feature: Allow node downtime during the simulation #110

Open
carlaKC opened this issue Sep 21, 2023 · 0 comments
Open

Feature: Allow node downtime during the simulation #110

carlaKC opened this issue Sep 21, 2023 · 0 comments
Assignees
Labels
Robustness Changes that improve the robustness of running the simulator simulationerrors Handling of errors than happen within the simulation.

Comments

@carlaKC
Copy link
Contributor

carlaKC commented Sep 21, 2023

This issue is similar to #32.

What do we do when an individual node that we have execution permissions on goes down?
Right now, the simplest approach is just to kill the simulation.

However, there are likely some simulation scenarios where it's useful to be able to take nodes offline for a while and bring them back online. Likewise, it can be useful to continue to run the simulation with a subset of the nodes that are working (for example, on a signet where people shut their laptops and kill their nodes).

Rather than dying, we can add a --keep-alive option to the simulation which would allow us to stay up for as long as any activity is successfully executing and die when we no longer have any actions that are working.

@carlaKC carlaKC added Robustness Changes that improve the robustness of running the simulator simulationerrors Handling of errors than happen within the simulation. labels Sep 21, 2023
@okjodom okjodom self-assigned this Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Robustness Changes that improve the robustness of running the simulator simulationerrors Handling of errors than happen within the simulation.
Projects
None yet
Development

No branches or pull requests

2 participants