2011-05-24 12:40:37 -04:00
|
|
|
start_server {tags {"scripting"}} {
|
|
|
|
test {EVAL - Does Lua interpreter replies to our requests?} {
|
|
|
|
r eval {return 'hello'} 0
|
|
|
|
} {hello}
|
|
|
|
|
|
|
|
test {EVAL - Lua integer -> Redis protocol type conversion} {
|
|
|
|
r eval {return 100.5} 0
|
|
|
|
} {100}
|
|
|
|
|
|
|
|
test {EVAL - Lua string -> Redis protocol type conversion} {
|
|
|
|
r eval {return 'hello world'} 0
|
|
|
|
} {hello world}
|
|
|
|
|
|
|
|
test {EVAL - Lua true boolean -> Redis protocol type conversion} {
|
|
|
|
r eval {return true} 0
|
|
|
|
} {1}
|
|
|
|
|
|
|
|
test {EVAL - Lua false boolean -> Redis protocol type conversion} {
|
|
|
|
r eval {return false} 0
|
|
|
|
} {}
|
|
|
|
|
|
|
|
test {EVAL - Lua status code reply -> Redis protocol type conversion} {
|
|
|
|
r eval {return {ok='fine'}} 0
|
|
|
|
} {fine}
|
|
|
|
|
|
|
|
test {EVAL - Lua error reply -> Redis protocol type conversion} {
|
|
|
|
catch {
|
|
|
|
r eval {return {err='this is an error'}} 0
|
|
|
|
} e
|
|
|
|
set _ $e
|
|
|
|
} {this is an error}
|
|
|
|
|
|
|
|
test {EVAL - Lua table -> Redis protocol type conversion} {
|
|
|
|
r eval {return {1,2,3,'ciao',{1,2}}} 0
|
|
|
|
} {1 2 3 ciao {1 2}}
|
|
|
|
|
2013-01-16 12:00:20 -05:00
|
|
|
test {EVAL - Are the KEYS and ARGV arrays populated correctly?} {
|
2011-05-24 12:40:37 -04:00
|
|
|
r eval {return {KEYS[1],KEYS[2],ARGV[1],ARGV[2]}} 2 a b c d
|
|
|
|
} {a b c d}
|
|
|
|
|
|
|
|
test {EVAL - is Lua able to call Redis API?} {
|
|
|
|
r set mykey myval
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {return redis.call('get',KEYS[1])} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {myval}
|
|
|
|
|
|
|
|
test {EVALSHA - Can we call a SHA1 if already defined?} {
|
2014-04-06 10:20:01 -04:00
|
|
|
r evalsha fd758d1589d044dd850a6f05d52f2eefd27f033f 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {myval}
|
|
|
|
|
2012-11-22 09:50:00 -05:00
|
|
|
test {EVALSHA - Can we call a SHA1 in uppercase?} {
|
2014-04-06 10:20:01 -04:00
|
|
|
r evalsha FD758D1589D044DD850A6F05D52F2EEFD27F033F 1 mykey
|
2012-11-22 09:50:00 -05:00
|
|
|
} {myval}
|
|
|
|
|
2011-10-25 05:19:15 -04:00
|
|
|
test {EVALSHA - Do we get an error on invalid SHA1?} {
|
|
|
|
catch {r evalsha NotValidShaSUM 0} e
|
|
|
|
set _ $e
|
|
|
|
} {NOSCRIPT*}
|
|
|
|
|
2011-05-24 12:40:37 -04:00
|
|
|
test {EVALSHA - Do we get an error on non defined SHA1?} {
|
2011-10-25 05:19:15 -04:00
|
|
|
catch {r evalsha ffd632c7d33e571e9f24556ebed26c3479a87130 0} e
|
2011-05-24 12:40:37 -04:00
|
|
|
set _ $e
|
|
|
|
} {NOSCRIPT*}
|
|
|
|
|
|
|
|
test {EVAL - Redis integer -> Lua type conversion} {
|
2016-04-25 09:49:57 -04:00
|
|
|
r set x 0
|
2011-05-24 12:40:37 -04:00
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('incr',KEYS[1])
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 x
|
2011-05-24 12:40:37 -04:00
|
|
|
} {number 1}
|
|
|
|
|
|
|
|
test {EVAL - Redis bulk -> Lua type conversion} {
|
|
|
|
r set mykey myval
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('get',KEYS[1])
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {string myval}
|
|
|
|
|
|
|
|
test {EVAL - Redis multi bulk -> Lua type conversion} {
|
|
|
|
r del mylist
|
|
|
|
r rpush mylist a
|
|
|
|
r rpush mylist b
|
|
|
|
r rpush mylist c
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('lrange',KEYS[1],0,-1)
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo[1],foo[2],foo[3],# foo}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mylist
|
2011-05-24 12:40:37 -04:00
|
|
|
} {table a b c 3}
|
|
|
|
|
|
|
|
test {EVAL - Redis status reply -> Lua type conversion} {
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('set',KEYS[1],'myval')
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo['ok']}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {table OK}
|
|
|
|
|
|
|
|
test {EVAL - Redis error reply -> Lua type conversion} {
|
|
|
|
r set mykey myval
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('incr',KEYS[1])
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo['err']}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {table {ERR value is not an integer or out of range}}
|
|
|
|
|
|
|
|
test {EVAL - Redis nil bulk reply -> Lua type conversion} {
|
|
|
|
r del mykey
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('get',KEYS[1])
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo == false}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {boolean 1}
|
|
|
|
|
Fix semantics of Lua calls to SELECT.
Lua scripts are executed in the context of the currently selected
database (as selected by the caller of the script).
However Lua scripts are also free to use the SELECT command in order to
affect other DBs. When SELECT is called frm Lua, the old behavior, before
this commit, was to automatically set the Lua caller selected DB to the
last DB selected by Lua. See for example the following sequence of
commands:
SELECT 0
SET x 10
EVAL "redis.call('select','1')" 0
SET x 20
Before this commit after the execution of this sequence of commands,
we'll have x=10 in DB 0, and x=20 in DB 1.
Because of the problem above, there was a bug affecting replication of
Lua scripts, because of the actual implementation of replication. It was
possible to fix the implementation of Lua scripts in order to fix the
issue, but looking closely, the bug is the consequence of the behavior
of Lua ability to set the caller's DB.
Under the old semantics, a script selecting a different DB, has no simple
ways to restore the state and select back the previously selected DB.
Moreover the script auhtor must remember that the restore is needed,
otherwise the new commands executed by the caller, will be executed in
the context of a different DB.
So this commit fixes both the replication issue, and this hard-to-use
semantics, by removing the ability of Lua, after the script execution,
to force the caller to switch to the DB selected by the Lua script.
The new behavior of the previous sequence of commadns is to just set
X=20 in DB 0. However Lua scripts are still capable of writing / reading
from different DBs if needed.
WARNING: This is a semantical change that will break programs that are
conceived to select the client selected DB via Lua scripts.
This fixes issue #1811.
2014-06-12 09:51:55 -04:00
|
|
|
test {EVAL - Is the Lua client using the currently selected DB?} {
|
2011-05-24 12:40:37 -04:00
|
|
|
r set mykey "this is DB 9"
|
|
|
|
r select 10
|
|
|
|
r set mykey "this is DB 10"
|
2016-04-25 09:49:57 -04:00
|
|
|
r eval {return redis.pcall('get',KEYS[1])} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {this is DB 10}
|
|
|
|
|
Fix semantics of Lua calls to SELECT.
Lua scripts are executed in the context of the currently selected
database (as selected by the caller of the script).
However Lua scripts are also free to use the SELECT command in order to
affect other DBs. When SELECT is called frm Lua, the old behavior, before
this commit, was to automatically set the Lua caller selected DB to the
last DB selected by Lua. See for example the following sequence of
commands:
SELECT 0
SET x 10
EVAL "redis.call('select','1')" 0
SET x 20
Before this commit after the execution of this sequence of commands,
we'll have x=10 in DB 0, and x=20 in DB 1.
Because of the problem above, there was a bug affecting replication of
Lua scripts, because of the actual implementation of replication. It was
possible to fix the implementation of Lua scripts in order to fix the
issue, but looking closely, the bug is the consequence of the behavior
of Lua ability to set the caller's DB.
Under the old semantics, a script selecting a different DB, has no simple
ways to restore the state and select back the previously selected DB.
Moreover the script auhtor must remember that the restore is needed,
otherwise the new commands executed by the caller, will be executed in
the context of a different DB.
So this commit fixes both the replication issue, and this hard-to-use
semantics, by removing the ability of Lua, after the script execution,
to force the caller to switch to the DB selected by the Lua script.
The new behavior of the previous sequence of commadns is to just set
X=20 in DB 0. However Lua scripts are still capable of writing / reading
from different DBs if needed.
WARNING: This is a semantical change that will break programs that are
conceived to select the client selected DB via Lua scripts.
This fixes issue #1811.
2014-06-12 09:51:55 -04:00
|
|
|
test {EVAL - SELECT inside Lua should not affect the caller} {
|
|
|
|
# here we DB 10 is selected
|
|
|
|
r set mykey "original value"
|
2011-10-20 10:02:23 -04:00
|
|
|
r eval {return redis.pcall('select','9')} 0
|
Fix semantics of Lua calls to SELECT.
Lua scripts are executed in the context of the currently selected
database (as selected by the caller of the script).
However Lua scripts are also free to use the SELECT command in order to
affect other DBs. When SELECT is called frm Lua, the old behavior, before
this commit, was to automatically set the Lua caller selected DB to the
last DB selected by Lua. See for example the following sequence of
commands:
SELECT 0
SET x 10
EVAL "redis.call('select','1')" 0
SET x 20
Before this commit after the execution of this sequence of commands,
we'll have x=10 in DB 0, and x=20 in DB 1.
Because of the problem above, there was a bug affecting replication of
Lua scripts, because of the actual implementation of replication. It was
possible to fix the implementation of Lua scripts in order to fix the
issue, but looking closely, the bug is the consequence of the behavior
of Lua ability to set the caller's DB.
Under the old semantics, a script selecting a different DB, has no simple
ways to restore the state and select back the previously selected DB.
Moreover the script auhtor must remember that the restore is needed,
otherwise the new commands executed by the caller, will be executed in
the context of a different DB.
So this commit fixes both the replication issue, and this hard-to-use
semantics, by removing the ability of Lua, after the script execution,
to force the caller to switch to the DB selected by the Lua script.
The new behavior of the previous sequence of commadns is to just set
X=20 in DB 0. However Lua scripts are still capable of writing / reading
from different DBs if needed.
WARNING: This is a semantical change that will break programs that are
conceived to select the client selected DB via Lua scripts.
This fixes issue #1811.
2014-06-12 09:51:55 -04:00
|
|
|
set res [r get mykey]
|
|
|
|
r select 9
|
|
|
|
set res
|
|
|
|
} {original value}
|
2011-05-24 12:40:37 -04:00
|
|
|
|
2011-10-31 11:09:07 -04:00
|
|
|
if 0 {
|
|
|
|
test {EVAL - Script can't run more than configured time limit} {
|
|
|
|
r config set lua-time-limit 1
|
|
|
|
catch {
|
|
|
|
r eval {
|
|
|
|
local i = 0
|
|
|
|
while true do i=i+1 end
|
|
|
|
} 0
|
|
|
|
} e
|
|
|
|
set _ $e
|
|
|
|
} {*execution time*}
|
|
|
|
}
|
2011-09-27 09:39:41 -04:00
|
|
|
|
|
|
|
test {EVAL - Scripts can't run certain commands} {
|
|
|
|
set e {}
|
2016-05-31 10:43:21 -04:00
|
|
|
catch {r eval {return redis.pcall('blpop','x',0)} 0} e
|
2011-09-27 09:39:41 -04:00
|
|
|
set e
|
|
|
|
} {*not allowed*}
|
|
|
|
|
|
|
|
test {EVAL - Scripts can't run certain commands} {
|
|
|
|
set e {}
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 0
|
2011-09-27 09:39:41 -04:00
|
|
|
catch {
|
2011-10-20 10:02:23 -04:00
|
|
|
r eval "redis.pcall('randomkey'); return redis.pcall('set','x','ciao')" 0
|
2011-09-27 09:39:41 -04:00
|
|
|
} e
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 1
|
2011-09-27 09:39:41 -04:00
|
|
|
set e
|
|
|
|
} {*not allowed after*}
|
|
|
|
|
2012-08-31 04:22:21 -04:00
|
|
|
test {EVAL - No arguments to redis.call/pcall is considered an error} {
|
|
|
|
set e {}
|
|
|
|
catch {r eval {return redis.call()} 0} e
|
|
|
|
set e
|
|
|
|
} {*one argument*}
|
|
|
|
|
2011-10-20 10:02:23 -04:00
|
|
|
test {EVAL - redis.call variant raises a Lua error on Redis cmd error (1)} {
|
|
|
|
set e {}
|
|
|
|
catch {
|
|
|
|
r eval "redis.call('nosuchcommand')" 0
|
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*Unknown Redis*}
|
|
|
|
|
|
|
|
test {EVAL - redis.call variant raises a Lua error on Redis cmd error (1)} {
|
|
|
|
set e {}
|
|
|
|
catch {
|
|
|
|
r eval "redis.call('get','a','b','c')" 0
|
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*number of args*}
|
|
|
|
|
|
|
|
test {EVAL - redis.call variant raises a Lua error on Redis cmd error (1)} {
|
|
|
|
set e {}
|
|
|
|
r set foo bar
|
|
|
|
catch {
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {redis.call('lpush',KEYS[1],'val')} 1 foo
|
2011-10-20 10:02:23 -04:00
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*against a key*}
|
2011-10-25 05:19:15 -04:00
|
|
|
|
2014-04-04 14:13:14 -04:00
|
|
|
test {EVAL - JSON numeric decoding} {
|
|
|
|
# We must return the table as a string because otherwise
|
|
|
|
# Redis converts floats to ints and we get 0 and 1023 instead
|
|
|
|
# of 0.0003 and 1023.2 as the parsed output.
|
|
|
|
r eval {return
|
|
|
|
table.concat(
|
|
|
|
cjson.decode(
|
|
|
|
"[0.0, -5e3, -1, 0.3e-3, 1023.2, 0e10]"), " ")
|
|
|
|
} 0
|
|
|
|
} {0 -5000 -1 0.0003 1023.2 0}
|
|
|
|
|
|
|
|
test {EVAL - JSON string decoding} {
|
|
|
|
r eval {local decoded = cjson.decode('{"keya": "a", "keyb": "b"}')
|
|
|
|
return {decoded.keya, decoded.keyb}
|
|
|
|
} 0
|
|
|
|
} {a b}
|
|
|
|
|
2014-04-04 17:20:04 -04:00
|
|
|
test {EVAL - cmsgpack can pack double?} {
|
|
|
|
r eval {local encoded = cmsgpack.pack(0.1)
|
|
|
|
local h = ""
|
|
|
|
for i = 1, #encoded do
|
|
|
|
h = h .. string.format("%02x",string.byte(encoded,i))
|
|
|
|
end
|
|
|
|
return h
|
|
|
|
} 0
|
|
|
|
} {cb3fb999999999999a}
|
|
|
|
|
|
|
|
test {EVAL - cmsgpack can pack negative int64?} {
|
|
|
|
r eval {local encoded = cmsgpack.pack(-1099511627776)
|
|
|
|
local h = ""
|
|
|
|
for i = 1, #encoded do
|
|
|
|
h = h .. string.format("%02x",string.byte(encoded,i))
|
|
|
|
end
|
|
|
|
return h
|
|
|
|
} 0
|
|
|
|
} {d3ffffff0000000000}
|
|
|
|
|
|
|
|
test {EVAL - cmsgpack can pack and unpack circular references?} {
|
|
|
|
r eval {local a = {x=nil,y=5}
|
|
|
|
local b = {x=a}
|
|
|
|
a['x'] = b
|
|
|
|
local encoded = cmsgpack.pack(a)
|
|
|
|
local h = ""
|
|
|
|
-- cmsgpack encodes to a depth of 16, but can't encode
|
|
|
|
-- references, so the encoded object has a deep copy recusive
|
|
|
|
-- depth of 16.
|
|
|
|
for i = 1, #encoded do
|
|
|
|
h = h .. string.format("%02x",string.byte(encoded,i))
|
|
|
|
end
|
|
|
|
-- when unpacked, re.x.x != re because the unpack creates
|
|
|
|
-- individual tables down to a depth of 16.
|
|
|
|
-- (that's why the encoded output is so large)
|
|
|
|
local re = cmsgpack.unpack(encoded)
|
|
|
|
assert(re)
|
|
|
|
assert(re.x)
|
|
|
|
assert(re.x.x.y == re.y)
|
|
|
|
assert(re.x.x.x.x.y == re.y)
|
|
|
|
assert(re.x.x.x.x.x.x.y == re.y)
|
|
|
|
assert(re.x.x.x.x.x.x.x.x.x.x.y == re.y)
|
|
|
|
-- maximum working depth:
|
|
|
|
assert(re.x.x.x.x.x.x.x.x.x.x.x.x.x.x.y == re.y)
|
|
|
|
-- now the last x would be b above and has no y
|
|
|
|
assert(re.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x)
|
|
|
|
-- so, the final x.x is at the depth limit and was assigned nil
|
|
|
|
assert(re.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x == nil)
|
|
|
|
return {h, re.x.x.x.x.x.x.x.x.y == re.y, re.y == 5}
|
|
|
|
} 0
|
|
|
|
} {82a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a178c0 1 1}
|
|
|
|
|
Lua: Add bitop
A few people have written custom C commands because bit
manipulation isn't exposed through Lua. Let's give
them Mike Pall's bitop.
This adds bitop 1.0.2 (2012-05-08) from http://bitop.luajit.org/
bitop is imported as "bit" into the global namespace.
New Lua commands: bit.tobit, bit.tohex, bit.bnot, bit.band, bit.bor, bit.bxor,
bit.lshift, bit.rshift, bit.arshift, bit.rol, bit.ror, bit.bswap
Verification of working (the asserts would abort on error, so (nil) is correct):
127.0.0.1:6379> eval "assert(bit.tobit(1) == 1); assert(bit.band(1) == 1); assert(bit.bxor(1,2) == 3); assert(bit.bor(1,2,4,8,16,32,64,128) == 255)" 0
(nil)
127.0.0.1:6379> eval 'assert(0x7fffffff == 2147483647, "broken hex literals"); assert(0xffffffff == -1 or 0xffffffff == 2^32-1, "broken hex literals"); assert(tostring(-1) == "-1", "broken tostring()"); assert(tostring(0xffffffff) == "-1" or tostring(0xffffffff) == "4294967295", "broken tostring()")' 0
(nil)
Tests also integrated into the scripting tests and can be run with:
./runtest --single unit/scripting
Tests are excerpted from `bittest.lua` included in the bitop distribution.
2014-04-04 11:34:36 -04:00
|
|
|
test {EVAL - Numerical sanity check from bitop} {
|
|
|
|
r eval {assert(0x7fffffff == 2147483647, "broken hex literals");
|
|
|
|
assert(0xffffffff == -1 or 0xffffffff == 2^32-1,
|
|
|
|
"broken hex literals");
|
|
|
|
assert(tostring(-1) == "-1", "broken tostring()");
|
|
|
|
assert(tostring(0xffffffff) == "-1" or
|
|
|
|
tostring(0xffffffff) == "4294967295",
|
|
|
|
"broken tostring()")
|
|
|
|
} 0
|
|
|
|
} {}
|
|
|
|
|
|
|
|
test {EVAL - Verify minimal bitop functionality} {
|
|
|
|
r eval {assert(bit.tobit(1) == 1);
|
|
|
|
assert(bit.band(1) == 1);
|
|
|
|
assert(bit.bxor(1,2) == 3);
|
|
|
|
assert(bit.bor(1,2,4,8,16,32,64,128) == 255)
|
|
|
|
} 0
|
|
|
|
} {}
|
|
|
|
|
2016-01-08 09:42:43 -05:00
|
|
|
test {EVAL - Able to parse trailing comments} {
|
|
|
|
r eval {return 'hello' --trailing comment} 0
|
|
|
|
} {hello}
|
|
|
|
|
2011-10-25 05:19:15 -04:00
|
|
|
test {SCRIPTING FLUSH - is able to clear the scripts cache?} {
|
|
|
|
r set mykey myval
|
2014-04-06 10:20:01 -04:00
|
|
|
set v [r evalsha fd758d1589d044dd850a6f05d52f2eefd27f033f 1 mykey]
|
2011-10-25 05:19:15 -04:00
|
|
|
assert_equal $v myval
|
|
|
|
set e ""
|
|
|
|
r script flush
|
2014-04-06 10:20:01 -04:00
|
|
|
catch {r evalsha fd758d1589d044dd850a6f05d52f2eefd27f033f 1 mykey} e
|
2011-10-25 05:19:15 -04:00
|
|
|
set e
|
|
|
|
} {NOSCRIPT*}
|
|
|
|
|
|
|
|
test {SCRIPT EXISTS - can detect already defined scripts?} {
|
|
|
|
r eval "return 1+1" 0
|
|
|
|
r script exists a27e7e8a43702b7046d4f6a7ccf5b60cef6b9bd9 a27e7e8a43702b7046d4f6a7ccf5b60cef6b9bda
|
|
|
|
} {1 0}
|
|
|
|
|
|
|
|
test {SCRIPT LOAD - is able to register scripts in the scripting cache} {
|
|
|
|
list \
|
|
|
|
[r script load "return 'loaded'"] \
|
|
|
|
[r evalsha b534286061d4b9e4026607613b95c06c06015ae8 0]
|
2011-10-25 08:46:15 -04:00
|
|
|
} {b534286061d4b9e4026607613b95c06c06015ae8 loaded}
|
2012-02-01 11:49:03 -05:00
|
|
|
|
|
|
|
test "In the context of Lua the output of random commands gets ordered" {
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 0
|
2012-02-01 11:49:03 -05:00
|
|
|
r del myset
|
|
|
|
r sadd myset a b c d e f g h i l m n o p q r s t u v z aa aaa azz
|
2018-09-05 13:47:29 -04:00
|
|
|
set res [r eval {return redis.call('smembers',KEYS[1])} 1 myset]
|
|
|
|
r debug lua-always-replicate-commands 1
|
|
|
|
set res
|
2012-02-01 11:49:03 -05:00
|
|
|
} {a aa aaa azz b c d e f g h i l m n o p q r s t u v z}
|
|
|
|
|
Scripting: Force SORT BY constant determinism inside SORT itself.
SORT is able to return (faster than when ordering) unordered output if
the "BY" clause is used with a constant value. However we try to play
well with scripting requirements of determinism providing always sorted
outputs when SORT (and other similar commands) are called by Lua
scripts.
However we used the general mechanism in place in scripting in order to
reorder SORT output, that is, if the command has the "S" flag set, the
Lua scripting engine will take an additional step when converting a
multi bulk reply to Lua value, calling a Lua sorting function.
This is suboptimal as we can do it faster inside SORT itself.
This is also broken as issue #545 shows us: basically when SORT is used
with a constant BY, and additionally also GET is used, the Lua scripting
engine was trying to order the output as a flat array, while it was
actually a list of key-value pairs.
What we do know is to recognized if the caller of SORT is the Lua client
(since we can check this using the REDIS_LUA_CLIENT flag). If so, and if
a "don't sort" condition is triggered by the BY option with a constant
string, we force the lexicographical sorting.
This commit fixes this bug and improves the performance, and at the same
time simplifies the implementation. This does not mean I'm smart today,
it means I was stupid when I committed the original implementation ;)
2012-09-04 19:12:41 -04:00
|
|
|
test "SORT is normally not alpha re-ordered for the scripting engine" {
|
2012-02-01 11:49:03 -05:00
|
|
|
r del myset
|
|
|
|
r sadd myset 1 2 3 4 10
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {return redis.call('sort',KEYS[1],'desc')} 1 myset
|
2012-02-01 11:49:03 -05:00
|
|
|
} {10 4 3 2 1}
|
|
|
|
|
Scripting: Force SORT BY constant determinism inside SORT itself.
SORT is able to return (faster than when ordering) unordered output if
the "BY" clause is used with a constant value. However we try to play
well with scripting requirements of determinism providing always sorted
outputs when SORT (and other similar commands) are called by Lua
scripts.
However we used the general mechanism in place in scripting in order to
reorder SORT output, that is, if the command has the "S" flag set, the
Lua scripting engine will take an additional step when converting a
multi bulk reply to Lua value, calling a Lua sorting function.
This is suboptimal as we can do it faster inside SORT itself.
This is also broken as issue #545 shows us: basically when SORT is used
with a constant BY, and additionally also GET is used, the Lua scripting
engine was trying to order the output as a flat array, while it was
actually a list of key-value pairs.
What we do know is to recognized if the caller of SORT is the Lua client
(since we can check this using the REDIS_LUA_CLIENT flag). If so, and if
a "don't sort" condition is triggered by the BY option with a constant
string, we force the lexicographical sorting.
This commit fixes this bug and improves the performance, and at the same
time simplifies the implementation. This does not mean I'm smart today,
it means I was stupid when I committed the original implementation ;)
2012-09-04 19:12:41 -04:00
|
|
|
test "SORT BY <constant> output gets ordered for scripting" {
|
2012-02-01 11:49:03 -05:00
|
|
|
r del myset
|
|
|
|
r sadd myset a b c d e f g h i l m n o p q r s t u v z aa aaa azz
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {return redis.call('sort',KEYS[1],'by','_')} 1 myset
|
2012-02-01 11:49:03 -05:00
|
|
|
} {a aa aaa azz b c d e f g h i l m n o p q r s t u v z}
|
|
|
|
|
Scripting: Force SORT BY constant determinism inside SORT itself.
SORT is able to return (faster than when ordering) unordered output if
the "BY" clause is used with a constant value. However we try to play
well with scripting requirements of determinism providing always sorted
outputs when SORT (and other similar commands) are called by Lua
scripts.
However we used the general mechanism in place in scripting in order to
reorder SORT output, that is, if the command has the "S" flag set, the
Lua scripting engine will take an additional step when converting a
multi bulk reply to Lua value, calling a Lua sorting function.
This is suboptimal as we can do it faster inside SORT itself.
This is also broken as issue #545 shows us: basically when SORT is used
with a constant BY, and additionally also GET is used, the Lua scripting
engine was trying to order the output as a flat array, while it was
actually a list of key-value pairs.
What we do know is to recognized if the caller of SORT is the Lua client
(since we can check this using the REDIS_LUA_CLIENT flag). If so, and if
a "don't sort" condition is triggered by the BY option with a constant
string, we force the lexicographical sorting.
This commit fixes this bug and improves the performance, and at the same
time simplifies the implementation. This does not mean I'm smart today,
it means I was stupid when I committed the original implementation ;)
2012-09-04 19:12:41 -04:00
|
|
|
test "SORT BY <constant> with GET gets ordered for scripting" {
|
2012-02-01 11:49:03 -05:00
|
|
|
r del myset
|
|
|
|
r sadd myset a b c
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {return redis.call('sort',KEYS[1],'by','_','get','#','get','_:*')} 1 myset
|
Scripting: Force SORT BY constant determinism inside SORT itself.
SORT is able to return (faster than when ordering) unordered output if
the "BY" clause is used with a constant value. However we try to play
well with scripting requirements of determinism providing always sorted
outputs when SORT (and other similar commands) are called by Lua
scripts.
However we used the general mechanism in place in scripting in order to
reorder SORT output, that is, if the command has the "S" flag set, the
Lua scripting engine will take an additional step when converting a
multi bulk reply to Lua value, calling a Lua sorting function.
This is suboptimal as we can do it faster inside SORT itself.
This is also broken as issue #545 shows us: basically when SORT is used
with a constant BY, and additionally also GET is used, the Lua scripting
engine was trying to order the output as a flat array, while it was
actually a list of key-value pairs.
What we do know is to recognized if the caller of SORT is the Lua client
(since we can check this using the REDIS_LUA_CLIENT flag). If so, and if
a "don't sort" condition is triggered by the BY option with a constant
string, we force the lexicographical sorting.
This commit fixes this bug and improves the performance, and at the same
time simplifies the implementation. This does not mean I'm smart today,
it means I was stupid when I committed the original implementation ;)
2012-09-04 19:12:41 -04:00
|
|
|
} {a {} b {} c {}}
|
2012-03-28 14:47:50 -04:00
|
|
|
|
|
|
|
test "redis.sha1hex() implementation" {
|
|
|
|
list [r eval {return redis.sha1hex('')} 0] \
|
|
|
|
[r eval {return redis.sha1hex('Pizza & Mandolino')} 0]
|
|
|
|
} {da39a3ee5e6b4b0d3255bfef95601890afd80709 74822d82031af7493c20eefa13bd07ec4fada82f}
|
2012-04-13 05:48:45 -04:00
|
|
|
|
|
|
|
test {Globals protection reading an undeclared global variable} {
|
|
|
|
catch {r eval {return a} 0} e
|
|
|
|
set e
|
2016-05-06 03:12:56 -04:00
|
|
|
} {*ERR*attempted to access * global*}
|
2012-04-13 05:48:45 -04:00
|
|
|
|
2012-04-13 07:40:57 -04:00
|
|
|
test {Globals protection setting an undeclared global*} {
|
2012-04-13 05:48:45 -04:00
|
|
|
catch {r eval {a=10} 0} e
|
|
|
|
set e
|
2012-04-13 07:40:57 -04:00
|
|
|
} {*ERR*attempted to create global*}
|
2012-04-13 09:23:32 -04:00
|
|
|
|
|
|
|
test {Test an example script DECR_IF_GT} {
|
|
|
|
set decr_if_gt {
|
|
|
|
local current
|
|
|
|
|
|
|
|
current = redis.call('get',KEYS[1])
|
|
|
|
if not current then return nil end
|
|
|
|
if current > ARGV[1] then
|
|
|
|
return redis.call('decr',KEYS[1])
|
|
|
|
else
|
|
|
|
return redis.call('get',KEYS[1])
|
|
|
|
end
|
|
|
|
}
|
|
|
|
r set foo 5
|
|
|
|
set res {}
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
set res
|
|
|
|
} {4 3 2 2 2}
|
2012-04-18 17:50:16 -04:00
|
|
|
|
|
|
|
test {Scripting engine resets PRNG at every script execution} {
|
|
|
|
set rand1 [r eval {return tostring(math.random())} 0]
|
|
|
|
set rand2 [r eval {return tostring(math.random())} 0]
|
|
|
|
assert_equal $rand1 $rand2
|
|
|
|
}
|
|
|
|
|
|
|
|
test {Scripting engine PRNG can be seeded correctly} {
|
|
|
|
set rand1 [r eval {
|
|
|
|
math.randomseed(ARGV[1]); return tostring(math.random())
|
|
|
|
} 0 10]
|
|
|
|
set rand2 [r eval {
|
|
|
|
math.randomseed(ARGV[1]); return tostring(math.random())
|
|
|
|
} 0 10]
|
|
|
|
set rand3 [r eval {
|
|
|
|
math.randomseed(ARGV[1]); return tostring(math.random())
|
|
|
|
} 0 20]
|
|
|
|
assert_equal $rand1 $rand2
|
|
|
|
assert {$rand2 ne $rand3}
|
|
|
|
}
|
2013-06-19 12:53:07 -04:00
|
|
|
|
2013-08-30 02:59:11 -04:00
|
|
|
test {EVAL does not leak in the Lua stack} {
|
|
|
|
r set x 0
|
|
|
|
# Use a non blocking client to speedup the loop.
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
for {set j 0} {$j < 10000} {incr j} {
|
|
|
|
$rd eval {return redis.call("incr",KEYS[1])} 1 x
|
|
|
|
}
|
|
|
|
for {set j 0} {$j < 10000} {incr j} {
|
|
|
|
$rd read
|
|
|
|
}
|
|
|
|
assert {[s used_memory_lua] < 1024*100}
|
|
|
|
$rd close
|
|
|
|
r get x
|
|
|
|
} {10000}
|
|
|
|
|
2013-06-19 12:53:07 -04:00
|
|
|
test {EVAL processes writes from AOF in read-only slaves} {
|
|
|
|
r flushall
|
|
|
|
r config set appendonly yes
|
2018-03-25 07:03:38 -04:00
|
|
|
r config set aof-use-rdb-preamble no
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {redis.call("set",KEYS[1],"100")} 1 foo
|
|
|
|
r eval {redis.call("incr",KEYS[1])} 1 foo
|
|
|
|
r eval {redis.call("incr",KEYS[1])} 1 foo
|
2013-06-19 12:53:07 -04:00
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[s aof_rewrite_in_progress] == 0
|
|
|
|
} else {
|
|
|
|
fail "AOF rewrite can't complete after CONFIG SET appendonly yes."
|
|
|
|
}
|
|
|
|
r config set slave-read-only yes
|
|
|
|
r slaveof 127.0.0.1 0
|
|
|
|
r debug loadaof
|
2014-05-07 10:04:45 -04:00
|
|
|
set res [r get foo]
|
|
|
|
r slaveof no one
|
|
|
|
set res
|
2013-06-19 12:53:07 -04:00
|
|
|
} {102}
|
2014-05-07 10:04:45 -04:00
|
|
|
|
|
|
|
test {We can call scripts rewriting client->argv from Lua} {
|
|
|
|
r del myset
|
|
|
|
r sadd myset a b c
|
|
|
|
r mset a 1 b 2 c 3 d 4
|
|
|
|
assert {[r spop myset] ne {}}
|
2014-03-11 10:38:55 -04:00
|
|
|
assert {[r spop myset 1] ne {}}
|
2014-05-07 10:04:45 -04:00
|
|
|
assert {[r spop myset] ne {}}
|
|
|
|
assert {[r mget a b c d] eq {1 2 3 4}}
|
|
|
|
assert {[r spop myset] eq {}}
|
|
|
|
}
|
2014-05-20 10:20:16 -04:00
|
|
|
|
|
|
|
test {Call Redis command with many args from Lua (issue #1764)} {
|
|
|
|
r eval {
|
|
|
|
local i
|
|
|
|
local x={}
|
|
|
|
redis.call('del','mylist')
|
|
|
|
for i=1,100 do
|
|
|
|
table.insert(x,i)
|
|
|
|
end
|
|
|
|
redis.call('rpush','mylist',unpack(x))
|
|
|
|
return redis.call('lrange','mylist',0,-1)
|
|
|
|
} 0
|
|
|
|
} {1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100}
|
2014-06-04 12:51:20 -04:00
|
|
|
|
|
|
|
test {Number conversion precision test (issue #1118)} {
|
|
|
|
r eval {
|
|
|
|
local value = 9007199254740991
|
|
|
|
redis.call("set","foo",value)
|
|
|
|
return redis.call("get","foo")
|
|
|
|
} 0
|
|
|
|
} {9007199254740991}
|
2014-06-10 14:21:37 -04:00
|
|
|
|
|
|
|
test {String containing number precision test (regression of issue #1118)} {
|
|
|
|
r eval {
|
|
|
|
redis.call("set", "key", "12039611435714932082")
|
|
|
|
return redis.call("get", "key")
|
|
|
|
} 0
|
|
|
|
} {12039611435714932082}
|
2014-06-28 22:20:44 -04:00
|
|
|
|
|
|
|
test {Verify negative arg count is error instead of crash (issue #1842)} {
|
|
|
|
catch { r eval { return "hello" } -12 } e
|
|
|
|
set e
|
|
|
|
} {ERR Number of keys can't be negative}
|
2014-08-17 10:32:26 -04:00
|
|
|
|
|
|
|
test {Correct handling of reused argv (issue #1939)} {
|
|
|
|
r eval {
|
|
|
|
for i = 0, 10 do
|
|
|
|
redis.call('SET', 'a', '1')
|
|
|
|
redis.call('MGET', 'a', 'b', 'c')
|
|
|
|
redis.call('EXPIRE', 'a', 0)
|
|
|
|
redis.call('GET', 'a')
|
|
|
|
redis.call('MGET', 'a', 'b', 'c')
|
|
|
|
end
|
|
|
|
} 0
|
|
|
|
}
|
2015-10-30 05:02:10 -04:00
|
|
|
|
|
|
|
test {Functions in the Redis namespace are able to report errors} {
|
|
|
|
catch {
|
|
|
|
r eval {
|
|
|
|
redis.sha1hex()
|
|
|
|
} 0
|
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*wrong number*}
|
2011-05-24 12:40:37 -04:00
|
|
|
}
|
2011-07-15 11:41:40 -04:00
|
|
|
|
2012-04-19 17:49:33 -04:00
|
|
|
# Start a new server since the last test in this stanza will kill the
|
|
|
|
# instance at all.
|
|
|
|
start_server {tags {"scripting"}} {
|
|
|
|
test {Timedout read-only scripts can be killed by SCRIPT KILL} {
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
r config set lua-time-limit 10
|
|
|
|
$rd eval {while true do end} 0
|
|
|
|
after 200
|
|
|
|
catch {r ping} e
|
|
|
|
assert_match {BUSY*} $e
|
|
|
|
r script kill
|
2014-04-24 12:21:12 -04:00
|
|
|
after 200 ; # Give some time to Lua to call the hook again...
|
2012-04-19 17:49:33 -04:00
|
|
|
assert_equal [r ping] "PONG"
|
|
|
|
}
|
|
|
|
|
2013-01-10 05:10:31 -05:00
|
|
|
test {Timedout script link is still usable after Lua returns} {
|
|
|
|
r config set lua-time-limit 10
|
|
|
|
r eval {for i=1,100000 do redis.call('ping') end return 'ok'} 0
|
|
|
|
r ping
|
|
|
|
} {PONG}
|
|
|
|
|
2012-04-19 17:49:33 -04:00
|
|
|
test {Timedout scripts that modified data can't be killed by SCRIPT KILL} {
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
r config set lua-time-limit 10
|
2014-04-06 10:20:01 -04:00
|
|
|
$rd eval {redis.call('set',KEYS[1],'y'); while true do end} 1 x
|
2012-04-19 17:49:33 -04:00
|
|
|
after 200
|
|
|
|
catch {r ping} e
|
|
|
|
assert_match {BUSY*} $e
|
|
|
|
catch {r script kill} e
|
2012-10-22 04:28:54 -04:00
|
|
|
assert_match {UNKILLABLE*} $e
|
2012-04-19 17:49:33 -04:00
|
|
|
catch {r ping} e
|
|
|
|
assert_match {BUSY*} $e
|
|
|
|
}
|
|
|
|
|
2013-01-10 05:10:31 -05:00
|
|
|
# Note: keep this test at the end of this server stanza because it
|
|
|
|
# kills the server.
|
2012-04-19 17:49:33 -04:00
|
|
|
test {SHUTDOWN NOSAVE can kill a timedout script anyway} {
|
2018-07-01 01:24:50 -04:00
|
|
|
# The server could be still unresponding to normal commands.
|
2012-04-19 17:49:33 -04:00
|
|
|
catch {r ping} e
|
|
|
|
assert_match {BUSY*} $e
|
|
|
|
catch {r shutdown nosave}
|
|
|
|
# Make sure the server was killed
|
|
|
|
catch {set rd [redis_deferring_client]} e
|
|
|
|
assert_match {*connection refused*} $e
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-10-30 05:18:25 -04:00
|
|
|
foreach cmdrepl {0 1} {
|
|
|
|
start_server {tags {"scripting repl"}} {
|
|
|
|
start_server {} {
|
|
|
|
if {$cmdrepl == 1} {
|
|
|
|
set rt "(commmands replication)"
|
2012-06-02 17:29:57 -04:00
|
|
|
} else {
|
2015-10-30 05:18:25 -04:00
|
|
|
set rt "(scripts replication)"
|
|
|
|
r debug lua-always-replicate-commands 1
|
2012-06-02 17:29:57 -04:00
|
|
|
}
|
2011-07-15 11:41:40 -04:00
|
|
|
|
2015-10-30 05:18:25 -04:00
|
|
|
test "Before the slave connects we issue two EVAL commands $rt" {
|
|
|
|
# One with an error, but still executing a command.
|
|
|
|
# SHA is: 67164fc43fa971f76fd1aaeeaf60c1c178d25876
|
|
|
|
catch {
|
|
|
|
r eval {redis.call('incr',KEYS[1]); redis.call('nonexisting')} 1 x
|
|
|
|
}
|
|
|
|
# One command is correct:
|
|
|
|
# SHA is: 6f5ade10a69975e903c6d07b10ea44c6382381a5
|
|
|
|
r eval {return redis.call('incr',KEYS[1])} 1 x
|
|
|
|
} {2}
|
|
|
|
|
2015-10-30 07:02:15 -04:00
|
|
|
test "Connect a slave to the master instance $rt" {
|
2015-10-30 05:18:25 -04:00
|
|
|
r -1 slaveof [srv 0 host] [srv 0 port]
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[s -1 role] eq {slave} &&
|
|
|
|
[string match {*master_link_status:up*} [r -1 info replication]]
|
|
|
|
} else {
|
|
|
|
fail "Can't turn the instance into a slave"
|
|
|
|
}
|
2013-01-10 05:10:31 -05:00
|
|
|
}
|
2011-07-15 11:41:40 -04:00
|
|
|
|
2015-10-30 05:18:25 -04:00
|
|
|
test "Now use EVALSHA against the master, with both SHAs $rt" {
|
|
|
|
# The server should replicate successful and unsuccessful
|
|
|
|
# commands as EVAL instead of EVALSHA.
|
|
|
|
catch {
|
|
|
|
r evalsha 67164fc43fa971f76fd1aaeeaf60c1c178d25876 1 x
|
|
|
|
}
|
|
|
|
r evalsha 6f5ade10a69975e903c6d07b10ea44c6382381a5 1 x
|
|
|
|
} {4}
|
|
|
|
|
|
|
|
test "If EVALSHA was replicated as EVAL, 'x' should be '4' $rt" {
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 get x] eq {4}
|
|
|
|
} else {
|
|
|
|
fail "Expected 4 in x, but value is '[r -1 get x]'"
|
|
|
|
}
|
2012-04-26 05:16:52 -04:00
|
|
|
}
|
A reimplementation of blocking operation internals.
Redis provides support for blocking operations such as BLPOP or BRPOP.
This operations are identical to normal LPOP and RPOP operations as long
as there are elements in the target list, but if the list is empty they
block waiting for new data to arrive to the list.
All the clients blocked waiting for th same list are served in a FIFO
way, so the first that blocked is the first to be served when there is
more data pushed by another client into the list.
The previous implementation of blocking operations was conceived to
serve clients in the context of push operations. For for instance:
1) There is a client "A" blocked on list "foo".
2) The client "B" performs `LPUSH foo somevalue`.
3) The client "A" is served in the context of the "B" LPUSH,
synchronously.
Processing things in a synchronous way was useful as if "A" pushes a
value that is served by "B", from the point of view of the database is a
NOP (no operation) thing, that is, nothing is replicated, nothing is
written in the AOF file, and so forth.
However later we implemented two things:
1) Variadic LPUSH that could add multiple values to a list in the
context of a single call.
2) BRPOPLPUSH that was a version of BRPOP that also provided a "PUSH"
side effect when receiving data.
This forced us to make the synchronous implementation more complex. If
client "B" is waiting for data, and "A" pushes three elemnents in a
single call, we needed to propagate an LPUSH with a missing argument
in the AOF and replication link. We also needed to make sure to
replicate the LPUSH side of BRPOPLPUSH, but only if in turn did not
happened to serve another blocking client into another list ;)
This were complex but with a few of mutually recursive functions
everything worked as expected... until one day we introduced scripting
in Redis.
Scripting + synchronous blocking operations = Issue #614.
Basically you can't "rewrite" a script to have just a partial effect on
the replicas and AOF file if the script happened to serve a few blocked
clients.
The solution to all this problems, implemented by this commit, is to
change the way we serve blocked clients. Instead of serving the blocked
clients synchronously, in the context of the command performing the PUSH
operation, it is now an asynchronous and iterative process:
1) If a key that has clients blocked waiting for data is the subject of
a list push operation, We simply mark keys as "ready" and put it into a
queue.
2) Every command pushing stuff on lists, as a variadic LPUSH, a script,
or whatever it is, is replicated verbatim without any rewriting.
3) Every time a Redis command, a MULTI/EXEC block, or a script,
completed its execution, we run the list of keys ready to serve blocked
clients (as more data arrived), and process this list serving the
blocked clients.
4) As a result of "3" maybe more keys are ready again for other clients
(as a result of BRPOPLPUSH we may have push operations), so we iterate
back to step "3" if it's needed.
The new code has a much simpler semantics, and a simpler to understand
implementation, with the disadvantage of not being able to "optmize out"
a PUSH+BPOP as a No OP.
This commit will be tested with care before the final merge, more tests
will be added likely.
2012-09-04 04:37:49 -04:00
|
|
|
|
2015-10-30 05:18:25 -04:00
|
|
|
test "Replication of script multiple pushes to list with BLPOP $rt" {
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
$rd brpop a 0
|
|
|
|
r eval {
|
|
|
|
redis.call("lpush",KEYS[1],"1");
|
|
|
|
redis.call("lpush",KEYS[1],"2");
|
|
|
|
} 1 a
|
|
|
|
set res [$rd read]
|
|
|
|
$rd close
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 lrange a 0 -1] eq [r lrange a 0 -1]
|
|
|
|
} else {
|
|
|
|
fail "Expected list 'a' in slave and master to be the same, but they are respectively '[r -1 lrange a 0 -1]' and '[r lrange a 0 -1]'"
|
|
|
|
}
|
|
|
|
set res
|
|
|
|
} {a 1}
|
|
|
|
|
|
|
|
test "EVALSHA replication when first call is readonly $rt" {
|
|
|
|
r del x
|
|
|
|
r eval {if tonumber(ARGV[1]) > 0 then redis.call('incr', KEYS[1]) end} 1 x 0
|
|
|
|
r evalsha 6e0e2745aa546d0b50b801a20983b70710aef3ce 1 x 0
|
|
|
|
r evalsha 6e0e2745aa546d0b50b801a20983b70710aef3ce 1 x 1
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 get x] eq {1}
|
|
|
|
} else {
|
|
|
|
fail "Expected 1 in x, but value is '[r -1 get x]'"
|
|
|
|
}
|
2014-02-13 06:25:44 -05:00
|
|
|
}
|
2014-06-12 10:20:30 -04:00
|
|
|
|
2015-10-30 05:18:25 -04:00
|
|
|
test "Lua scripts using SELECT are replicated correctly $rt" {
|
|
|
|
r eval {
|
|
|
|
redis.call("set","foo1","bar1")
|
|
|
|
redis.call("select","10")
|
|
|
|
redis.call("incr","x")
|
|
|
|
redis.call("select","11")
|
|
|
|
redis.call("incr","z")
|
|
|
|
} 0
|
|
|
|
r eval {
|
|
|
|
redis.call("set","foo1","bar1")
|
|
|
|
redis.call("select","10")
|
|
|
|
redis.call("incr","x")
|
|
|
|
redis.call("select","11")
|
|
|
|
redis.call("incr","z")
|
|
|
|
} 0
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 debug digest] eq [r debug digest]
|
|
|
|
} else {
|
|
|
|
fail "Master-Slave desync after Lua script using SELECT."
|
|
|
|
}
|
2014-06-12 10:20:30 -04:00
|
|
|
}
|
|
|
|
}
|
2011-07-15 11:41:40 -04:00
|
|
|
}
|
|
|
|
}
|
2015-10-30 07:02:15 -04:00
|
|
|
|
|
|
|
start_server {tags {"scripting repl"}} {
|
2018-03-25 07:03:38 -04:00
|
|
|
start_server {overrides {appendonly yes aof-use-rdb-preamble no}} {
|
2015-10-30 07:02:15 -04:00
|
|
|
test "Connect a slave to the master instance" {
|
|
|
|
r -1 slaveof [srv 0 host] [srv 0 port]
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[s -1 role] eq {slave} &&
|
|
|
|
[string match {*master_link_status:up*} [r -1 info replication]]
|
|
|
|
} else {
|
|
|
|
fail "Can't turn the instance into a slave"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
test "Redis.replicate_commands() must be issued before any write" {
|
|
|
|
r eval {
|
|
|
|
redis.call('set','foo','bar');
|
|
|
|
return redis.replicate_commands();
|
|
|
|
} 0
|
|
|
|
} {}
|
|
|
|
|
|
|
|
test "Redis.replicate_commands() must be issued before any write (2)" {
|
|
|
|
r eval {
|
|
|
|
return redis.replicate_commands();
|
|
|
|
} 0
|
|
|
|
} {1}
|
|
|
|
|
|
|
|
test "Redis.set_repl() must be issued after replicate_commands()" {
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 0
|
2015-10-30 07:02:15 -04:00
|
|
|
catch {
|
|
|
|
r eval {
|
|
|
|
redis.set_repl(redis.REPL_ALL);
|
|
|
|
} 0
|
|
|
|
} e
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 1
|
2015-10-30 07:02:15 -04:00
|
|
|
set e
|
|
|
|
} {*only after turning on*}
|
|
|
|
|
|
|
|
test "Redis.set_repl() don't accept invalid values" {
|
|
|
|
catch {
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
redis.set_repl(12345);
|
|
|
|
} 0
|
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*Invalid*flags*}
|
|
|
|
|
|
|
|
test "Test selective replication of certain Redis commands from Lua" {
|
|
|
|
r del a b c d
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
redis.call('set','a','1');
|
|
|
|
redis.set_repl(redis.REPL_NONE);
|
|
|
|
redis.call('set','b','2');
|
|
|
|
redis.set_repl(redis.REPL_AOF);
|
|
|
|
redis.call('set','c','3');
|
|
|
|
redis.set_repl(redis.REPL_ALL);
|
|
|
|
redis.call('set','d','4');
|
|
|
|
} 0
|
|
|
|
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 mget a b c d] eq {1 {} {} 4}
|
|
|
|
} else {
|
|
|
|
fail "Only a and c should be replicated to slave"
|
|
|
|
}
|
|
|
|
|
|
|
|
# Master should have everything right now
|
|
|
|
assert {[r mget a b c d] eq {1 2 3 4}}
|
|
|
|
|
|
|
|
# After an AOF reload only a, c and d should exist
|
|
|
|
r debug loadaof
|
|
|
|
|
|
|
|
assert {[r mget a b c d] eq {1 {} 3 4}}
|
|
|
|
}
|
|
|
|
|
|
|
|
test "PRNG is seeded randomly for command replication" {
|
|
|
|
set a [
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
return math.random()*100000;
|
|
|
|
} 0
|
|
|
|
]
|
|
|
|
set b [
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
return math.random()*100000;
|
|
|
|
} 0
|
|
|
|
]
|
|
|
|
assert {$a ne $b}
|
|
|
|
}
|
|
|
|
|
|
|
|
test "Using side effects is not a problem with command replication" {
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
redis.call('set','time',redis.call('time')[1])
|
|
|
|
} 0
|
|
|
|
|
|
|
|
assert {[r get time] ne {}}
|
|
|
|
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r get time] eq [r -1 get time]
|
|
|
|
} else {
|
|
|
|
fail "Time key does not match between master and slave"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|