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

Too much downtime involved in server restart. #228

Open
kfogel opened this issue Jul 19, 2017 · 1 comment
Open

Too much downtime involved in server restart. #228

kfogel opened this issue Jul 19, 2017 · 1 comment

Comments

@kfogel
Copy link
Member

kfogel commented Jul 19, 2017

Certain maintenance operations involve a server restart (e.g., the temporary enablement of the /signup route for account creation, which of course will go away once issue #138 is resolved). Those server restarts involve

$ ./node_modules/.bin/forever stopall
$ ./node_modules/.bin/forever -da start --watchDirectory . -l forever.log -o out.log -e err.log ./bin/www

...and the second step often takes too long to bring the server back up and/or needs to be run twice. There is a possibility that the real issue is that the first step takes too long to complete (i.e., the prompt comes back, but the stopall command is not yet actually done stopping everything), and therefore the first time the second command is run it's a no-op because the stopping is still going on. This needs some more investigation.

But basically, restarts should be near-instantaneous. Whatever we need to do to accomplish that, we should do.

@kfogel
Copy link
Member Author

kfogel commented Jul 19, 2017

Yes, further experimentation seems to confirm the hypothesis above: wait a little longer after stopall, and be rewarded with a much faster startup time in the start command.

@kfogel kfogel assigned kfogel and unassigned kfogel Sep 1, 2017
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

1 participant