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
Is there any reason the master cant have access to the cache data (or even the cache itself)? It looks like the cache will return keys and can be cleared via reset(). I was looking to show the cache contents (from an express server running in the master) just for status/debugging, but the best i can do is show the keys. Thanks!
The text was updated successfully, but these errors were encountered:
Hi @texels,
In a clustered environment, I'm not used to set any logic in the master process. To me, it should only serve as a kind of proxy for its workers. That's why I enforced consuming cache data from the workers.
Let me think about it and come back when I decide if I should make that change.
Is there any reason the master cant have access to the cache data (or even the cache itself)? It looks like the cache will return keys and can be cleared via reset(). I was looking to show the cache contents (from an express server running in the master) just for status/debugging, but the best i can do is show the keys. Thanks!
The text was updated successfully, but these errors were encountered: