-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Return to latest powerstate #136
Comments
This comment has been minimized.
This comment has been minimized.
Why rethink? It's still open isn't it? |
This was opened a long time ago and i thought i'd bump it as it kinda disappeared. |
When is this going to be done? |
Eventually. Its not a trivial task with the current state of the daemon. |
why has this been open for nearly 3 years? This is a very useful and basic feature of even docker itself. |
It's still open because no one implemented it so far, feel free to do so. |
Age of an issue does not determine the priority of implementation. In addition, I've already given this a swing once and it was significantly more difficult to properly implement than imagined, which is why it is still here. |
This comment has been minimized.
This comment has been minimized.
closed for now in pterodactyl/wings@85762ba |
The return to the previous state only works in some containers (ex: minecraft), in the custom containers or Voice Server containers do not work. I don't know if it's my fault but it doesn't seem to be. |
So what are we supposed to do in case of a an unexpected shutdown? Re-start manually all servers? Genuinely confused |
The issue is closed. It's implemented in the 1.0 betas.
On stable, yes. |
It's been eight years since this was first proposed, and two years since the last comment on the idea. Was this just dropped and forgotten, or is someone actually working on this? |
This issue is closed. That means that this is implemented. 1.0 was released a long time ago. |
As discussed on Discord, a feature which will return the servers on one node to their power state before a potential crash of the Daemon or an unplanned reboot / crash of the host system will reduce the stress on an admin to remember the correct state of each server before.
This could be further improved by allowing the following three settings upon a daemon coming online:
To avoid load spikes, a defineable delay between starting the servers will be beneficial. (30 seconds should be a good value to start with).
Let me know if this fit's here or should be more a daemon feature.
The text was updated successfully, but these errors were encountered: