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

Checkpoint and Restore #17103

Closed
juancampa opened this issue Nov 17, 2017 · 2 comments
Closed

Checkpoint and Restore #17103

juancampa opened this issue Nov 17, 2017 · 2 comments
Labels
question Issues that look for answers.

Comments

@juancampa
Copy link

Hi, I was reading through @hashseed's proposal in #17058 and started wondering if this could be used to "checkpoint & restore" a running node program. I understand that a process is more than just the isolate and contexts (i.e there are OS-level resources like file descriptors, sockets, etc that are not serializable). But assuming that it would be acceptable to lose that part of the state. Is this something that is currently possible? would this be enabled or facilitated by the #17058 proposal?

I was picturing something like: send a signal to a running node.js process (i.e. kill –USR2 3049) and cause it to: wait until the current callstack is finished, serialize the state into a file, and exit. Later the same program could be restored by providing the file to a new process. Of course any file/network IO would have to be manually restored at this point.

Basically something like CRIU but specifically for node.js which could make it potentially faster and space efficient.

@tniessen tniessen added the question Issues that look for answers. label Nov 17, 2017
@refack
Copy link
Contributor

refack commented Nov 17, 2017

Hello @juancampa,

Check out the discussion in #13877

@juancampa
Copy link
Author

Thanks @refack. I also asked on #17058 and got a direct answer here: #17058 (comment)

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

No branches or pull requests

3 participants