Warning in production env

[jashsayani]

The application worked fine in prod, but when I switched from EJS to Handlebars, I started getting the following error on sails lift (in prod):

Warning: connection.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.

[bhanuc]

Are you using any session store ?

[mikedevita]

This isn't an issue. You haven't defined anything in config/session.js as a result sails defaults to memory for session storage.. its just warning you, as it can be a performance hog. When you set your NODE_ENV=production or you tell sails the environment: 'production' it auto generates this warning if you haven't set a session store up.

In a production env you should use something like redis, which is what SailsJs is built to use... See the docs here.

More specifically config/session.js outlines this information as comments.

[pixelfreak]

@mikedevita I have a follow-up question about this. I am not using any session in my code so how can I make sure there won't be memory leak in prod? Should I just ignore this warning?

[gotmikhail]

Should I still get this warning if I have session middleware disabled altogether?

[mikermcneil]

For future reference, there's more information and tips on diagnosing memory leaks in Node apps, and on reproducing+reporting suspected memory leaks in Sails here:
#3782 (comment)

[mikermcneil]

Also, see sailsjs.org/documentation/concepts/deployment for more info on deploying to production.