Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about master #5

Open
texels opened this issue Apr 5, 2017 · 2 comments
Open

Question about master #5

texels opened this issue Apr 5, 2017 · 2 comments

Comments

@texels
Copy link

texels commented Apr 5, 2017

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!

@PaquitoSoft
Copy link
Owner

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.

Thanks.

@endel
Copy link

endel commented May 9, 2017

Hey @texels, I've recently started a project called memshared which works very similarly with memored.

You can access the data from the master process and it should also work with fork, without relying strictly on the cluster module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants