-
Notifications
You must be signed in to change notification settings - Fork 104
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
Crash trying to shut down the ProcessSupervisor #154
Comments
Hi Matt, Thank for the bug report. There is something about the shutdown process that doesn't make 100% sense. I believe this is during a regular shutdown. It would be very helpful if you could reproduce this in a test in Horde. Can I ask you to make a PR with that? Eventually I want to have some good tests using |
So I can try to reproduce the issue in the example application though I'm not sure what I'm doing differently to make this happen. Running Here is the entire output from
|
Perhaps I'm doing something wrong so please correct me if I have.
I have 5 different registries/supervisors to split the load of my application. One for "everything else" and 4 for one particular entity which I've split up by hashing the name of the worker and starting the workers under that supervisor (and registering the name in that registry).
I'm using local-cluster with dynamic supervision (and the example nodewatching genserver) for testing where I see this the most, but it also happens when two machines connect together.
It doesn't say why the
ProcessSupervisor
shut down before this error occurred, so I assume it was a normal shutdown. Any ideas?The text was updated successfully, but these errors were encountered: