cluster-service

Turns your single process code into a fault-resilient multi-process service with built-in REST & CLI support

cluster-service

npm install cluster-service

https://npmjs.org/package/cluster-service

Turn your single process code into a fault-resilient, multi-process service with
built-in REST & CLI support. Restart or hot upgrade your web servers with zero
downtime or impact to clients.

Presentation:

http://x.co/bpnode

Video:

http://x.co/bpnodevid

Your existing application, be it console app or service of some kind:

// server.js
console.log("Hello World");

Leveraging cluster-service without adding a line of code:

npm install -g cluster-service
cservice "server.js" --accessKey "lksjdf982734"
// cserviced "server.js" --accessKey "lksjdf982734" // daemon

This can be done without a global install as well, by updating your package.json:

"scripts": {
    "start": "cservice server.js --accessKey lksjdf982734"
},
"dependencies": {
    "cluster-service": ">=0.5.0"
}

Now we can leverage npm to find our local install of cluster-service:

npm start

Or, if you prefer to control cluster-service within your code, we've got you covered:

// server.js
require("cluster-service").start({ workers: "./worker.js", accessKey: "lksjdf982734" });

// worker.js
console.log("Hello World"); // notice we moved our original app logic to the worker

Now that your service is resilient to worker failure, and utilizing all cores of your machine, lets talk to it. With your service running, type into the command-line:

restart all

or for a full list of commands...

help

or for help on a specific command:

help {command}

We can also issue commands from a seperate process, or even a remote machine (assuming proper access):

npm install -g cluster-service
cservice "restart all" --accessKey "my_access_key"

You can even pipe raw JSON for processing:

cservice "restart all" --accessKey "my_access_key" --json

Check out Cluster Commands for more.

When initializing your service, you have a number of options available:

cservice "server.js" --accessKey "123"

Or via JSON config:

cservice "config.json"

Or within your node app:

// server.js
// inline options
require("cluster-service").start({ workers: "worker.js", accessKey: "123" });
// or via config
require("cluster-service").start({ config: "config.json" });
  • workers - Path of worker to start. A string indicates a single worker, forked based on value of workerCount. An object indicates one or more worker objects: { "worker1": { worker: "worker1.js", cwd: process.cwd(), count: 2, restart: true } }. This option is automatically set if run via command-line cservice "worker.js" if the .js extension is detected.
  • accessKey - A secret key that must be specified if you wish to invoke commands from outside your process. Allows CLI & REST interfaces.
  • config - A filename to the configuration to load. Useful to keep options from having to be inline. This option is automatically set if run via command-line cservice "config.json" if the .json extension is detected.
  • host (default: "localhost") - Host to bind to for REST interface. (Will only bind if accessKey is provided)
  • port (default: 11987) - Port to bind to. If you leverage more than one cluster-service on a machine, you'll want to assign unique ports. (Will only bind if accessKey is provided)
  • workerCount (default: os.cpus().length) - Gives you control over the number of processes to run the same worker concurrently. Recommended to be 2 or more to improve availability. But some workers do not impact availability, such as task queues, and can be run as a single instance.
  • cli (default: true) - Enable the command line interface. Can be disabled for background services, or test cases. Running cserviced will automatically disable the CLI.
  • ssl - If provided, will bind using HTTPS by passing this object as the TLS options.
  • run - Ability to run a command, output result, and exit. This option is automatically set if run via command-line cservice "restart all" and no extension is detected.
  • json (default: false) - If specified in conjunction with run, will only output the result in JSON for consumption from other tasks/services. No other data will be output.
  • silent (default: false) - If true, forked workers will not send their output to parent's stdio.
  • allowHttpGet (default: false) - For development purposes, can be enabled for testing, but is not recommended otherwise.
  • restartOnMemUsage (default: disabled) - If a worker process exceeds the specified memory threshold (in bytes), the process will be restarted gracefully. Only one worker will be restarted at a time.
  • restartOnUpTime (default: disabled) - If a worker process exceeds the specified uptime threshold (in seconds), the process will be restarted gracefully. Only one worker will be restarted at a time.
  • commands - A single directory, an array of directories, or a comma-delimited list of directories may be provided to auto-register commands found in the provided folders that match the ".js" extension. If the module exposes the "id" property, that will be the name of the command, otherwise the filename (minus the extension) will be used as the name of the command. If relative paths are provided, they will be resolved from process.cwd().
  • master - An optional module to execute for the master process only, once start has been completed.

A DPS Cluster Service has two interfaces, the console (stdio), and an HTTP REST API. The two interfaces are treated identical, as console input/output is piped over the REST API. The reason for the piping is that a DPS Cluster Service is intentionally designed to only support one instance of the given service running at any one time, and the port binding is the resource constraint. This allows secondary services to act as console-only interfaces as they pipe all input/output over HTTP to the already running service that owns the port. This flow enables the CLI to background processes. The REST API is locked to a "accessKey" expected in the query string. The console automatically passes this key to the REST API, but for external REST API access, the key will need to be known.

{ host: "localhost", port: 11987, accessKey: "lksjdf982734" }

Invoking the REST interface directly would look something like:

curl -d "" "http://localhost:11987/cli?cmd=help&accessKey=lksjdf982734"

Or better yet, use the run option to do the work for you:

cservice "help" --accessKey "lksjdf982734"
// same as
cservice --run "help" --accessKey "lksjdf982734"

While a Cluster Service may provide its own custom commands, below are provided out-of-the-box. Commands may be disabled by overriding them.

  • start workerPath [cwd] { [timeout:60] } - Gracefully start service, one worker at a time.
  • restart all|pid { [timeout:60] } - Gracefully restart service, waiting up to timeout before terminating workers.
  • shutdown all|pid { [timeout:60] } - Gracefully shutdown service, waiting up to timeout before terminating workers.
  • exit now - Forcefully exits the service.
  • help [cmd] - Get help.
  • upgrade all|pid workerPath { [cwd] [timeout:60] } - Gracefully upgrade service, one worker at a time. (continuous deployment support).
  • workers - Returns list of active worker processes.
  • health - Returns health of service. Can be overidden by service to expose app-specific data.
  • info - Returns summary of process & workers.

Creating custom, or overriding commands and events is as simple as:

cservice "server.js" --commands "./commands,../some_more_commands"

Or if you prefer to manually do so via code:

var cservice = require("cluster-service");
cservice.on("custom", function(evt, cb, arg1, arg2) { // "custom" command
    // can also fire custom events
    cservice.trigger("on.custom.complete", 1, 2, 3);
};

cservice.on("test", function(evt, cb, testScript, timeout) { // we're overriding the "test" command
    // arguments
    // do something, no callback required (events may optionally be triggered)
}; 

// can also issue commands programatically
cservice.trigger("custom", function(err) { /* my callback */ }, "arg1value", "arg2value");

Events are emitted to interested parties.

  • workerStart (pid, reason) - Upon exit of any worker process, the process id of the exited worker. Reasons include: "start", "restart", "failure", and "upgrade".
  • workerExit (pid, reason) - Upon start of any worker process. Reasons include: "start", "restart", "failure", and "upgrade".

While web servers are automatically wired up and do not require async logic (as of v1.0), if your service requires any other asynchronous initialization code before being ready, this is how it can be done.

Have the worker inform the master once it is actually ready:

// worker.js
require("cluster-service").workerReady(false); // we're NOT ready!
setTimeout(funtion() {
    // dumb example of async support
    require("cluster-service").workerReady(); // we're ready!
}, 1000);

Additionally, a worker may optionally perform cleanup tasks prior to exit, via:

// worker.js
require("cluster-service").workerReady({
    onWorkerStop: function() {
        // lets clean this place up
        process.exit(); // we're responsible for exiting if we register this cb
    }
});

Commands may be granted "inproc" (high risk), "local" (low risk), or "remote" (no risk). Setting access control can be done within the command, like so:

// exit.js 
module.exports.control = function(){
    return "local";
};

Or may be overriden at runtime via:

// server.js 
require("cluster-service").control({ "exit": "local" });

Download and install:

git clone https://github.com/godaddy/node-cluster-service.git
cd node-cluster-service
npm install

Now test:

npm test

View code coverage in any browser:

coverage/lcov-report/index.html

Change Log

MIT