Close socket on any exception #130
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anti-social
force-pushed
the
dev/close-socket-on-exception
branch
2 times, most recently
from
1d40693 to
206cef5
Compare
anti-social
force-pushed
the
dev/close-socket-on-exception
branch
from
206cef5 to
83f3a07
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have a problem with python-memcached and celery. Sometimes our tasks get incorrect data from memcache.
This is because celery send
SIGUSR1signal to the worker process that exceeds soft time limit. The worker handle that signal and raisesSoftTimeLimitExceededexception. If this happened between writing and reading from socket received data remains in the socket. Thus next task receives them.