[Question]: Warning concerning connect.session() MemoryStore not designed for prod environment #1014
-
Contact DetailsNo response What is your question?I've encountered the following warning, doesn't install confidence. Could this be fixed? More DetailsWhat is the main subject of your question?Other ScreenshotsNo response Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
|
The dependency issuing a warning is only being used for OpenID. This is not a concern if you aren’t using it, and minimal if your user base is not in the 1000s. The MemoryStore can be mitigated with redis or db. This app in is “pre-release”, meaning it’s not tuned up to production levels across the board, and this is one such area where this is the case. There are several other caches created in the servers lifespan that would greatly benefit from using Redis, and some architecture is already there to support it, but is not a priority until we get to a release state. I’ll plan to add more documentation for this and a more informative warning for admins using OpenID oauth. |
Beta Was this translation helpful? Give feedback.
-
|
Single file where |
Beta Was this translation helpful? Give feedback.
-
|
It’s also not a concern if you aren’t needing to spin up several instances of the server. |
Beta Was this translation helpful? Give feedback.
-
|
Does it mean that we cannot run more than 1 kubernetes Pod for librechat api service? |
Beta Was this translation helpful? Give feedback.
-
|
Not at all, you would just need to use redis as a memory store to be shared across all instances |
Beta Was this translation helpful? Give feedback.
-
|
Actually addressing this in an upcoming PR but will require use of Redis |
Beta Was this translation helpful? Give feedback.
-
|
Hello, we are having memory leaking problems in our production instance of librechat while using OIDC. Was this problem dealt with in a PR as you mentioned here? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, try using Redis |
Beta Was this translation helpful? Give feedback.
The dependency issuing a warning is only being used for OpenID. This is not a concern if you aren’t using it, and minimal if your user base is not in the 1000s.
The MemoryStore can be mitigated with redis or db. This app in is “pre-release”, meaning it’s not tuned up to production levels across the board, and this is one such area where this is the case. There are several other caches created in the servers lifespan that would greatly benefit from using Redis, and some architecture is already there to support it, but is not a priority until we get to a release state.
I’ll plan to add more documentation for this and a more informative warning for admins using OpenID oauth.