You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation uses only one connection per configured redis server. This connection is shared between the tree view operations and CLI commands for all users. Therefor its not working well with multiple commands used via CLI:
To fix these issues the connection handling must be rewritten to use multiple connections per database.
Main connection list may be used as is - but only for operations related to the UI tree view (fetch folder and keys for display on upper part of UI) (=> base connection). These one connect automatically on server start.
On first use of CLI new connection is cloned from base connection (ioredis duplicate()) and used for all CLI commands only (lazy initialize)
must introduce kind of user session handling to have one redis connection per user per CLI.
Connections must be closed if user session expires/not used anymore. Very important for pub/sub and multi!
If implemented increment minor version number of RC.
The text was updated successfully, but these errors were encountered:
sseide
changed the title
Rework backend to use mulptile redis connections for tree view and CLI
Rework backend to use multiple redis connections for tree view and CLI
Dec 27, 2019
Current implementation uses only one connection per configured redis server. This connection is shared between the tree view operations and CLI commands for all users. Therefor its not working well with multiple commands used via CLI:
To fix these issues the connection handling must be rewritten to use multiple connections per database.
Connections must be closed if user session expires/not used anymore. Very important for pub/sub and multi!
If implemented increment minor version number of RC.
The text was updated successfully, but these errors were encountered: