Use MAX_LOCK_TTL in RedisLockManager to avoid premature lock expiration
authorAaron Schulz <aschulz@wikimedia.org>
Fri, 30 Sep 2016 13:36:35 +0000 (06:36 -0700)
committerAaron Schulz <aschulz@wikimedia.org>
Fri, 30 Sep 2016 13:36:41 +0000 (06:36 -0700)
commite1505ff742140b04dc8ff8bbc1d9fb12ccdbc2a0
treea407bec89502e3c6cd94ccc7692f75246122a2a6
parenta2dd3480daf66e449bcddaa2b2b4f634e006bea6
Use MAX_LOCK_TTL in RedisLockManager to avoid premature lock expiration

App servers should not lower the redis structure TTL of locks set
from CLI scripts, which is what would typically happen before if
they touched the same keys. Instead, keep a high lock record TTL
and rely on the logical TTLs for expiry semantics.

Change-Id: I2948369845c47d2682a85dd0564673f3b813be83
includes/libs/lockmanager/RedisLockManager.php