You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that redis 2.2 (when used) will correctly pass the lualock code (which it doesn't seem like it should) and then it will blowup with errors such as 'unknown command 'EVALSHA''.
An example log we hit that shows this (on ubuntu precise which has redis 2.2):
Avoid using lua locks
The default redis library will try to be smart about using
or not using lua based locks, it seems to not correctly predict
this correctly and then fails with errors such as:
''unknown command 'EVALSHA''
Upstream issue filed:
redis/redis-py#550
The 'traditional' locks require PEXPIRE used by the redis-py
library which requires redis 2.6+ to actually work. So when
we are using a server version that is not new enough
we should conditionally raise a not implemented error to
avoid it later failing (which it will).
This also fixes a bunch of encoding issues that the enabling
of the py33 system now exposed (damn encodings...)
Change-Id: Ied6045276c9a1398db710a68aa75fe92aac9b4bb
It appears that redis 2.2 (when used) will correctly pass the lualock code (which it doesn't seem like it should) and then it will blowup with errors such as 'unknown command 'EVALSHA''.
An example log we hit that shows this (on ubuntu precise which has redis 2.2):
http://logs.openstack.org/42/131442/1/check/gate-tooz-python33/e4560c5/console.html
The text was updated successfully, but these errors were encountered: