tricycle/lesswrong — pull request #42 by johnsoft (2012-08-30 03:59:25+00:00)
Title: Issue 337 - Possible fix for spurious lock errors

http://code.google.com/p/lesswrong/issues/detail?id=337&colspec=ID%20Estimate%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Contributions

My guess is that something is causing the lock keys to not be deleted. So - if we tell memcached to expire the key sooner than the polling timeout period, then even if there's a mistake somewhere and a key isn't deleted, it will right itself after a delay.

So this will only (possibly) fix the symptoms and not the underlying problem, but it's still a quick and easy fix. If this doesn't help I'll probably add generous logging and try to piece things together from that.