I am trying to get my hands on the forked workers but I can't seem to find a way. I've looked at the code and it appears that the workers are spawned and forgotten.

Is this correct? If so would it be possible to add handles and a method to access them?

I appologize if I'm missing something obvious, I'm new to node.js processes.

Not sure why this is. It's like the first one is being ignored.

Maybe because npm-www starts up 2 servers?

This project has not had a lot of activity. I would like to see some new features like:

• Transform streams for workers stdout: So you could append process id etc to logs bubbling up from the workers
• onMessage is supported, but what about exit, online etc.
• .exit in the REPL is not exactly right, I think that sock.end() is what people are looking for, update documentation/implementation.
• Additional REPL features (some listed elsewhere), but I would like to be able to attach stdout for a given worker to the REPL...

Should I make some PR's or should I fork the project and start anew?

Hi all, I've been working on a tool to identify instances of events registered to the wrong object in uses of some JavaScript event-driven APIs, as part of a research project.
The tool flagged line 213 in cluster-master.js in the root of this repository, on the registration of the “end” event.

The reason I believe this is indicative of an error is as follows (from looking at the nodejs repl API documentation).
This listener for “end” is registered on variable r, which is an object of type repl.REPLServer, initialized on line 138 by a call to repl.start(). However, “end” is not an event emitted on repl.REPLServer.

My guess is that maybe instead you should be listening for “exit” (an event on repl.REPLServer), or “close” (an event on readline.Interface, which repl.REPLServer extends).

Thanks!

Ie, a worker should be able to do process.send({cmd: 'field', key: 'gitsha', value: 'dead134fdecafbad00aaabbb' }) and then in the workers object in the repl, you'll see gitsha: 'dead134fdecafbad00aaabbb'

All the debug outputs are always printed on the console.

Hi,

Is it possible to use this module to handle reading files?

Thanks

I started my node server app from root crontab, using cluster-master and even though I had "repl:3001" set, the repl seems to have not started.
netstat showed no listener on 3001.
on startup, I did see the message: "resize and then setup repl"

crontab invoked this script:

!/bin/sh

cd /home/jloveman/callhome2
/usr/bin/screen -dmS callhome2 sudo node /home/jloveman/callhome2/cluster_worker.js

And node knows it:

process.on("SIGKILL", function(){})
Error: uv_signal_start EINVAL

I think you're always hitting your catch.

We recently moved from pm2 to using supervisor with cluster-master, application yesterday went down due to a fatal error and I've this in logs:

dgram.js:147
  newHandle.lookup = self._handle.lookup;
                                 ^
TypeError: Cannot set property 'lookup' of undefined
    at replaceHandle (dgram.js:147:20)

Could you please give some insights on this, like if this issue is because of cluster-master or some wrong implementation from my side.

i'm technically not allowed to use this module as a missing license indicates all rights reserved. lawyers suck but corporate likes them.

any way you could slap mit or bsd in here somewhere? :)

disconnect -> cluster.workers[worker.id].disconnect()

kill - > cluster.workers[worker.id].process.kill()

Others?