req.session.passport (passportjs) is null when run with recluster. about recluster HOT 3 CLOSED

I commented on this by email, but it doesn't appear to have made it. Apologies if it does eventually make it and this comment appears twice.

I've used recluster with passport just fine in the past. What debugging have you done? Have you pinpointed the problem to a recluster problem? It seems unlikely to be recluster since that's just a wrapper around Node's cluster module. Are you using in-memory sessions? If so, each HTTP request has a chance of being handled by a different cluster worker, so unless it happens to be handled by the worker that created the session, then you'll have problems.

from recluster.

Thanks for quick response. Yes I am using in memory session, and that's probably the cause of it. I'll figure it out.

from recluster.

You're welcome. It's worth remembering that each (re-)cluster worker is a separate process and they don't share memory with each other. You either need a single worker (if you're just using recluster for it's restart features) or else an out-of-process session store such as Redis.

On 5 Sep 2014, at 17:46, Ashish Thakwani [email protected] wrote:

Thanks for quick response. Yes I am using in memory session, and that's probably the cause of it. I'll figure it out.

—
Reply to this email directly or view it on GitHub.

from recluster.