100% CPU

[techpines]

Hi, when I start this for some reason. I am seeing CPU spike to 100% when using with the cluster module:

MongoStore = require('socket.io-mongo')

cluster = require('cluster')
numCPUs = require('os').cpus().length;

// This is what the workers will do.
workers = function() {
    io = require('socket.io').listen(8080);

    io.configure(function() {
        io.set('store', new MongoStore())
    })
}

// Start forking if you are the master
if (cluster.isMaster) {
    for (var i = 0; i < numCPUs; i++) { cluster.fork() } 
} else { workers() }

node: 0.8.14
socket.io-mongo: 0.0.8
socket.io: 0.9.13

[kof]

I need to update to the latest mubsub version, it should be fixed there.

[techpines]

@kof is there maybe an older npm version for "socket.io-mongo" where the code is working?

[kof]

I think this bug was the whole time there, but it was not always reproducible.

[kof]

If you wait some days I will migrate to the new version of mubsub. Do you want to use it in production?

[techpines]

Yea, I wanted to use it in production.

[tanepiper]

@kof awesome - also wonder if you're looking into the issue with {safe: true} that keeps popping up? I couldn't see a way to pass in that option

[kof]

I think you can pass proper options already.

[zaneclaes]

I'm seeing this same issue -- 100% CPU usage with cluster. I'm using node.js 0.8.12 and the latest versions of all modules.

[kof]

heh ... need to find time to finally complete this one #3

[zaneclaes]

Ack, I wish I had read through the issues before moving this from my staging server (which doesn't use cluster) to production (which does). #kaboom there goes my whole server array :(

[kof]

actually this issue should exist also without cluster

[zaneclaes]

Is there any way I can easily work around this? I'm in a tight spot -- I just pushed a whole bunch of code to production, and my servers are now down. I hate to do a rollback, but it may be the only option...

[kof]

try to merge this pull .... #3 also good to know if it works ... haven't checked yet ... tests are not running but probably it works for you ...

[zaneclaes]

Please excuse my ignorance -- is there a way to install the pull with NPM?