-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
possible to set memcache 'expire' on locks? #12
Comments
#13 Will that work for you? |
@arvenil You are awesome! It is up to you to merge this into master branch. The potential racing problem is pretty hard to deal with. I don't want people complain about ninjia-mutex because of this change; changing my code to use flock or mySQL is probably easier. |
Awesome :) No worries, the Thanks for your issue report! :) |
#12: Add expiration time for memcache lock storage
Resolved by https:/arvenil/ninja-mutex/releases/tag/0.5.0 |
Hi, First of all thanks for the great library! Here I have some problems with un-released locks.
I am calling many 3rd party libraries between lock & release. Very occasionally I could get a fatal crash that the lock is never cleaned up.
My process typically takes 3~5 sec to complete, is it possible to set an expire value for the lock?
E.g. 60 sec, so it is not locked forever.
I could see the alternative maybe using flock so file system handles it...
My code is very simple like this:
The text was updated successfully, but these errors were encountered: