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

slicer crashing port issues #622

Closed
jsnoble opened this issue Nov 21, 2017 · 0 comments
Closed

slicer crashing port issues #622

jsnoble opened this issue Nov 21, 2017 · 0 comments

Comments

@jsnoble
Copy link
Member

jsnoble commented Nov 21, 2017

As the code stands now, when the slicer crashes, it comes back up and then sends a message to cluster master to shutdown everything which is the correct behavior, but it leads to slicer exiting twice. On the node master it tries to reclaim the port every time a slicer exits. Since it exits twice it sends the same port twice back into the port queue which can lead to port already in use errors in the future

jsnoble added a commit to jsnoble/teraslice that referenced this issue Nov 29, 2017
jsnoble added a commit to jsnoble/teraslice that referenced this issue Nov 29, 2017
@kstaken kstaken closed this as completed in 30fe7c9 Dec 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants