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

Show restart message after successful dump-load/snapshot-restore #230

Open
rymsha opened this issue Jun 25, 2020 · 4 comments
Open

Show restart message after successful dump-load/snapshot-restore #230

rymsha opened this issue Jun 25, 2020 · 4 comments
Assignees

Comments

@rymsha
Copy link
Contributor

rymsha commented Jun 25, 2020

It should be recommended, and in future versions even required to restart entire cluster (all nodes shutdown when all nodes stated up again) after successful
enonic snapshot restore (with any parameters)
and
enonic dump load (with any parameters)

Message could be something like:
"Please, restart all nodes of the cluster"

@rymsha rymsha changed the title Show message after successful dump-load/snapshot-restore Show restart message after successful dump-load/snapshot-restore Jun 25, 2020
@alansemenov
Copy link
Member

"Please, restart all nodes of the cluster"

This can be really confusing if you are not running XP in a cluster... I guess we have no way of figuring this out, so the message should be something like:

"The dump has been successfully loaded. If you are running XP in a cluster, make sure to restart all the nodes".
or
"The snapshot has been successfully restored. If you are running XP in a cluster, make sure to restart all the nodes".

@rymsha
Copy link
Contributor Author

rymsha commented Jun 25, 2020

For a single node it should also be restarted.

@alansemenov
Copy link
Member

Then it should be something node-unrelated, like "Please restart all running instances of XP"

@sigdestad
Copy link
Member

Ack to Alan's suggestion

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

4 participants