Skip to content
master
Switch branches/tags
Go to file
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 

Reloading a server in Node.js

The problem

Sometimes we could need reload a server without cut off the connections. We can use the "close" call and wait to the established connections, because "close" stops the server from accepting new connections. But in case we are using WebSockets the "close" call is not enough, becase a WebSocket could not finish in days. So we need a way to be able to detect if a WebSocket is in idle status to kill it and the solution is the server-shutdown module (@mitmaro).

This example

This example is based in two different examples:

Usage

node server/server.js

Example

  1. In a shell launch the master script:
$ node server/master.js
[6974] : Started master with 6974
[6980] :     Listeting at http://localhost:8100
[6980] :     A client (wqHAB1KF2Tl0dDrnAAAA) has connected
[...]
[6974] : Reloading...
[7011] :     Listeting at http://localhost:8100
[6974] : Sending SIGHUP signal to my child 6980
[6980] :     SIGHUP signal got. Exit graceluffy.
[6980] :     server end graceluffy.
[7011] :     A client (pYw7AtZHggIaFVu7AAAA) has connected
[...]
[6974] : stopping all...
[6974] : Sending SIGTERM signal to my child 7011
[7011] :     SIGTERM signal got. Exit now.
  1. In another shell we send the signals:
$ kill -SIGHUP 6974
$ kill -SIGTERM 6974

About

An example about reload Node.js gracefully without cut off active connections

Topics

Resources

License

Releases

No releases published

Packages

No packages published