Photo by Aleksandar Cvetanovic on Unsplash
It is important to shutdown correctly your apps to handle well processing requests and prevent it to accept new ones. I'll take a web server as example.
const http = require('http');
const server = http.createServer(function (req, res) {
setTimeout(function () {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('Hello World\n');
}, 4000);
}).listen(9090, function (err) {
console.log('listening http://localhost:9090/');
console.log('pid is ' + process.pid);
});
As we see our server doesn't shutdown properly and processing requests don't get right responses. First of all we need to understand how a Node process is terminated in order to fix it.
A process receives a signal when it is about to be killed. They are different kind of signals. We will focus on three of them in particular:
- SIGINT: Quit from keyboard (Ctrl + C).
- SIGQUIT: Quit from keyboard (Ctrl + \). It also produce a core dump file.
- SIGTERM: Quit from operating system (using kill command for example).
Node.js emits events when the process receives signals. You can write a handler for these events. In this one we will close our server so it deals with pending requests and prevent getting new ones.
// ...
function handleExit(signal) {
console.log(`Received ${signal}. Close my server properly.`)
server.close(function () {
process.exit(0);
});
}
process.on('SIGINT', handleExit);
process.on('SIGQUIT', handleExit);
process.on('SIGTERM', handleExit);
Now our server handles well the request then shutdown correctly. You can read more in Nairi Harutyunyan's nice article. It explain in details how to shutdown properly a server with a database.
It also exists an node module that handles this logic for you called death (made by JP Richardson).
const ON_DEATH = require('death')
ON_DEATH(function(signal, err) {
// clean up code here
})
Sometimes it is not enough
I ran into a situation recently where my server needed to accept new requests in order to shutdown properly. I'll give some explanations. My server subscribed to a webhook. This webhook has a limited quota of subscriptions. So if I don't want to exceed this quota I need to unsubscribe properly when my server shutdown. Here is the unsubscription workflow:
- Send a request to the webhhook to unsubscribe
- The webhook sent a request to the server to confirm unsubscription
- The server must respond with a specific token to validate the unsubscription
A Node.js process will close automatically if its event loop is empty. As you can see between 1. and 2. the event loop is empty so the process will be terminated and we won't be able to unsubscribe successfully.
Here is the new server codebase we will use:
const server = http.createServer(function (req, res) {
const params = qs.decode(req.url.split("?")[1]);
if (params.mode) {
res.writeHead(200);
res.write(params.challenge);
res.end();
} else {
let body = "";
req.on("data", chunk => {
body += chunk;
});
req.on("end", () => {
console.log('event', JSON.parse(body))
res.writeHead(200);
res.end();
});
}
}).listen(9090, function (err) {
console.log('listening http://localhost:9090/');
console.log('pid is ' + process.pid);
fetch('http://localhost:3000/webhook?mode=subscribe&callback=http://localhost:9090')
});
There are two changes. When the server starts listening on port 9090 we send a first request to subscribe our server to the webhook.
// ...
fetch('http://localhost:3000/webhook?mode=subscribe&callback=http://localhost:9090')
// ...
We also changed our server's request handler to let him confirm the subscription to the webhook by responding with the token called challenge.
// ...
if (params.mode) {
res.writeHead(200);
res.write(params.challenge);
res.end();
} else {
// ...
}
// ...
Let's change the handleExit function's implementation to send a request to our webhook. We ask the webhook to unsubcribe our server.
function handleExit(signal) {
console.log(`Received ${signal}. Close my server properly.`)
fetch('http://localhost:3000/webhook?mode=unsubscribe&callback=http://localhost:9090')
}
We need to update the code that responds with the challenge to kill our server's process when the webhook confirms the unsubscription.
// ...
if (params.mode) {
res.writeHead(200);
res.write(params.challenge);
res.end();
if (params.mode === 'unsubscribe') {
server.close(function () {
process.exit(0);
});
}
} else {
// ...
}
// ...
When the webhook confirms the unsubscription, we close our server so it stops getting new requests and exits our process properly. This is how the Twitch API webhooks subscription/unsubscription works.
Let's see how our server acts when we try to shut it down. I added some logs to make it more visual.
As you can see, it doesn't shutdown properly. The server's process is terminated before we get the webhook request that confirms unsubscription. So the webhook keeps sending events to our server.
To fix this we need to prevent the Node.js process from exiting. We can use the method process.stdin.resume that causes the process to pause and override disable default behavior like exiting on Ctrl+C.
const http = require('http');
process.stdin.resume();
// ...
And now?
Nice, it now waits for the confirmation before exiting the process.
I made a repository with all the sources presented in this article.
Hope it will help 🙌
Feedback is appreciated 🙏 Please tweet me if you have any questions @YvonnickFrin!
Top comments (3)
<snark>Saw the title and thought "Meh, just run:
</snark>Heh.
Pardon the utter sarcasm. I'm known for my burning dislike of JS, but I own that as personal. Every tool has valid uses, JS and Node.js included. If you like the technology and it works, more power to you!
In any case, this looks thorough and beautifully written, and I'm sure it will be super helpful to someone. It actually made sense to me, and I don't know the first thing about Node.js!
Thank you Jason, really nice comment ❤️
Great Read!
I'm all-new to .js, apologies if its a noob question;
is this helpful with PWA's?
Google Chrome Beta
and my back-up PC capabilities are driving me crazy!
Best,
C-Brennan-P