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

Fix issue #403 #428

Merged
merged 1 commit into from Jan 7, 2013
Merged

Fix issue #403 #428

merged 1 commit into from Jan 7, 2013

Conversation

herberteuler
Copy link
Contributor

Hi Nathan, I believe this patch fixes issue #403.

You are right, it was not race condition, but rather some already closed sockets might be left in the new cached sockets map, due to the wrong invocation to dissoc.

nathanmarz added a commit that referenced this pull request Jan 7, 2013
@nathanmarz nathanmarz merged commit d5bb376 into nathanmarz:master Jan 7, 2013
@xiaokang
Copy link
Contributor

Hi @herberteuler and @nathanmarz . I verified that cached sockets map does not remove closed zmq socket by logging. But I can not explain why the closed zmq socket will be used since the :cached-task->node+port map is updated correctlly.

@herberteuler
Copy link
Contributor Author

@xiaokang You may need to check if the old node+port that the dead worker used has been reassigned to run a new worker. If this happens, the same old node+port will still be needed and used.

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