René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"cluster: suicide flag is not set on master when calling disconnect from a worker","articleBody":"From the documentation:\n\n[`worker.suicide`](https://nodejs.org/api/cluster.html#cluster_worker_suicide):\n\n\u003e Set by calling .kill() or .disconnect(), until then it is undefined.\n\n[`worker.disconnect()`](https://nodejs.org/api/cluster.html#cluster_worker_disconnect):\n\n\u003e In a worker, this function will close all servers, wait for the 'close' event on those servers, and then disconnect the IPC channel.\n\u003e \n\u003e Causes .suicide to be set.\n\nRepro:\n\n``` javascript\nvar cluster = require('cluster');\n\nif (cluster.isMaster) {\n  // Master forks and listens for events\n  var worker = cluster.fork();\n  cluster.on('disconnect', function(){\n    console.log(\"disconnect\", worker.suicide);\n  });\n  cluster.on('exit', function(){\n    console.log(\"exit\", worker.suicide);\n  });\n} else {\n  // Worker just disconnects\n  cluster.worker.disconnect();\n}\n```\n\nIn node v0.10, both log statements would print `true` for `worker.suicide`. In 41b75ca9263f368db790fbdcc3963bb1a8c5cb7e, which landed during the v0.11 branch, this was broken, and all versions up to node v4 will print `false`. This is because `worker.disconnect()`, when called from the worker, does not send the `suicide` message anymore -- only `worker.destroy()` will send that message to the master.\n","author":{"url":"https://github.com/dpatti","@type":"Person","name":"dpatti"},"datePublished":"2015-10-07T15:25:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/3238/node/issues/3238"}