a1feda2388
RESP3: Scripting RESP3 mode set/map protocol -> Lua conversion.
2019-01-09 17:00:29 +01:00
9330bcc7ee
RESP3: Fix API in scripting.c leaving Lua conversions RESP2.
2019-01-09 17:00:29 +01:00
f07f3d729f
RESP3: Use new aggregate reply API in slowlog.c.
2019-01-09 17:00:29 +01:00
feb6b31832
RESP3: Use new aggregate reply API in t_set.c.
2019-01-09 17:00:29 +01:00
dcbd40cea4
RESP3: Use new aggregate reply API in cluster.c.
2019-01-09 17:00:29 +01:00
c7f80e4f1a
RESP3: Make WITHSCORES reply back with a flat array in RESP2.
2019-01-09 17:00:29 +01:00
fe67418ba4
RESP3: Use new deferred len API in object.c.
2019-01-09 17:00:29 +01:00
13966522ea
RESP3: bring RESP2 compatibility to previous changes.
2019-01-09 17:00:29 +01:00
e14aabf936
RESP3: addReply*Len() support for RESP2 backward comp.
2019-01-09 17:00:29 +01:00
1ac6926647
RESP3: put RESP version in the client structure.
2019-01-09 17:00:29 +01:00
f44e00b691
RESP3: Use new API and types in t_hash.c.
2019-01-09 17:00:29 +01:00
b507654716
RESP3: Use new deferred len API in dict.c.
2019-01-09 17:00:29 +01:00
cdd10193c5
RESP3: Use new deferred len API in config.c.
2019-01-09 17:00:29 +01:00
470c28380f
RESP3: Use new deferred len API in t_zset.c.
2019-01-09 17:00:29 +01:00
a577230a58
RESP3: Use new deferred len API in t_string.c.
2019-01-09 17:00:29 +01:00
07bce54093
RESP3: Use new deferred len API in replication.c.
2019-01-09 17:00:29 +01:00
073293693e
RESP3: Use new deferred len API in server.c.
2019-01-09 17:00:29 +01:00
57c5a766a2
RESP3: Aggregate deferred lengths functions.
2019-01-09 17:00:29 +01:00
914ee43108
RESP3: Double replies and aggregate lengths initial functions.
2019-01-09 17:00:29 +01:00
511298578a
Merge pull request #5746 from UmanShahzad/old-geohash-docs
...
Remove documentation about geohash-int in deps repo.
2019-01-09 10:12:09 +01:00
14400d073b
Merge pull request #5729 from artix75/cluster_manager_fix_cmd
...
Cluster Manager del-node: use CLUSTER RESET in place of SHUTDOWN
2019-01-09 10:11:27 +01:00
896be4c908
Merge pull request #5751 from chenyang8094/unstable
...
Update ae.c
2019-01-09 10:10:53 +01:00
30d8d05cd6
Update ae.c
...
Update comment
2019-01-06 15:01:25 +08:00
cc47dacd18
Remove documentation about geohash-int in deps repo.
2019-01-03 19:12:45 +05:00
17797660f1
Cluster Manager del-node: use CLUSTER RESET in place of SHUTDOWN
...
See issue #5687
2018-12-27 17:20:42 +01:00
e504583b78
Merge branch 'unstable' of github.com:/antirez/redis into unstable
2018-12-21 11:39:15 +01:00
638db2fc01
Merge pull request #5713 from artix75/cluster_manager_fix_cmd
...
Cluster Manager: enable --cluster-replace also for 'fix' command.
2018-12-19 17:34:35 +01:00
503fd229e4
Cluster Manager: enable --cluster-replace also for 'fix' command.
2018-12-19 17:29:25 +01:00
f07205e48c
Merge pull request #5709 from artix75/cluster_manager_fix_cmd
...
Fixed memory leak in clusterManagerCompareKeysValues.
2018-12-19 17:24:38 +01:00
cc29590188
Fixed memory leak in clusterManagerCompareKeysValues.
2018-12-18 18:45:10 +01:00
0d166674f9
Merge pull request #5708 from artix75/cluster_manager_fix_cmd
...
Cluster Manager: compare key values after BUSYKEY error (migration).
2018-12-18 18:27:38 +01:00
143bfa1e6e
Cluster Manager: compare key values after BUSYKEY error (migration).
...
If a key exists in the target node during a migration (BUSYKEY),
the value of the key on both nodes (source and target) will be compared.
If the key has the same value on both keys, the migration will be
automatically retried with the REPLACE argument in order to override
the target's key.
If the key has different values, the behaviour will depend on such
cases:
- In case of 'fix' command, the migration will stop and the user
will be warned to manually check the key(s).
- In other cases (ie. reshard), if the user launched the command
with the --cluster-replace option, the migration will be
retried with the REPLACE argument, elsewhere the migration will
stop and the user will be warned.
2018-12-18 17:45:35 +01:00
81008bf99e
Merge pull request #5691 from artix75/cluster_manager_fix_cmd
...
Cluster Manager: avoid using reply error messages to check slot status.
2018-12-12 13:39:53 +01:00
d935cfcb89
Cluster Manager: avoid using reply error messages to check slot status.
...
Slot assignment status is now checked by using CLUSTER SLOTS.
Furthermore, one memory leak has been fixed.
2018-12-12 13:34:43 +01:00
009a929269
Remove debugging printf from replication.tcl test.
2018-12-12 11:55:30 +01:00
129f2d2746
freeMemoryIfNeeded() small refactoring.
...
Related to issue #5686 and PR #5689 .
2018-12-12 11:37:15 +01:00
7ae184bfea
Merge pull request #5689 from soloestoy/donot-evict-when-AOF-loading
...
evict: don't care about mem if loading
2018-12-12 11:29:10 +01:00
03e2bb0cfd
Crashing is too much in addReplyErrorLength().
...
See #5663 .
2018-12-11 17:50:18 +01:00
b9cd89d108
evict: don't care about mem if loading
...
When loading data, we call processEventsWhileBlocked
to process events and execute commands.
But if we are loading AOF it's dangerous, because
processCommand would call freeMemoryIfNeeded to evict,
and that will break data consistency, see issue #5686 .
2018-12-12 00:25:58 +08:00
0110e46f6e
Merge branch 'unstable' of github.com:/antirez/redis into unstable
2018-12-11 13:30:04 +01:00
a31ca8d753
stringmatchlen() fuzz test added.
...
Verified to be able to trigger at least #5632 . Does not report other
issues.
2018-12-11 13:29:30 +01:00
c710d4afdc
Fix stringmatchlen() read past buffer bug.
...
See #5632 .
2018-12-11 13:18:52 +01:00
f77edf4234
Merge pull request #5665 from louiszhw/unstable
...
fix comments fault discription
2018-12-11 13:03:09 +01:00
e8529d1b1e
Merge pull request #4264 from lsytj0413/unstable
...
fix a typo: craeted -> created
2018-12-11 13:02:28 +01:00
11d399dded
Merge pull request #5684 from soloestoy/ignore-multi-cmd-flags-loading-aof
...
multi: ignore multiState's cmd_flags when loading AOF
2018-12-11 12:57:25 +01:00
6100be7d82
fix typo
2018-12-11 19:53:54 +08:00
1530c0a7dd
multi: ignore multiState's cmd_flags when loading AOF
2018-12-11 19:47:36 +08:00
274531396c
Reject EXEC containing write commands against RO replica.
...
Thanks to @soloestoy for discovering this issue in #5667 .
This is an alternative fix in order to avoid both cycling the clients
and also disconnecting clients just having valid read-only transactions
pending.
2018-12-11 11:39:21 +01:00
086363babf
Merge pull request #5681 from artix75/cluster_manager_fix_cmd
...
Cluster manager fix cmd
2018-12-11 08:23:54 +01:00
27ddb2ba3a
Cluster Manager:
...
- Multiple owners checking in 'fix'/'check' commands is now
optional (using --cluster-search-multiple-owners).
- Updated help.
2018-12-10 18:01:18 +01:00