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.

Sign up for GitHub

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

Jump to bottom

All hooks should link to the Cachex supervisor, not the main process #32

Closed
whitfin opened this issue May 21, 2016 · 0 comments · Fixed by #33
Closed

All hooks should link to the Cachex supervisor, not the main process #32

whitfin opened this issue May 21, 2016 · 0 comments · Fixed by #33
Assignees
@whitfin
Labels
bug enhancement

Comments

@whitfin
Copy link
Owner

whitfin commented May 21, 2016 •
edited
Loading

As it currently stands, hooks are started in the main process rather than inside the Cachex Supervisor. This means that hooks can crash without being restarted, causing backlogs in message queues and eventual memory issues.

This needs resolving ASAP as starting a cache from a spawn will have all your hooks die on startup, even though your cache will still be alive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@whitfin whitfin

Labels
bug enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ensure Hooks are linked to the Cachex Supervisor whitfin/cachex
1 participant
@whitfin