- 22 Jul, 2019 1 commit
-
-
Oran Agra authored
Other changes: * fix memory leak in error handling of rdb loading of type OBJ_MODULE
-
- 17 Jul, 2019 1 commit
-
-
Oran Agra authored
now that replica can read rdb directly from the socket, it should avoid exiting on short read and instead try to re-sync. this commit tries to have minimal effects on non-diskless rdb reading. and includes a test that tries to trigger this scenario on various read cases.
-
- 08 Jul, 2019 1 commit
-
-
Oran Agra authored
The implementation of the diskless replication was currently diskless only on the master side. The slave side was still storing the received rdb file to the disk before loading it back in and parsing it. This commit adds two modes to load rdb directly from socket: 1) when-empty 2) using "swapdb" the third mode of using diskless slave by flushdb is risky and currently not included. other changes: -------------- distinguish between aof configuration and state so that we can re-enable aof only when sync eventually succeeds (and not when exiting from readSyncBulkPayload after a failed attempt) also a CONFIG GET and INFO during rdb loading would have lied When loading rdb from the network, don't kill the server on short read (that can be a network error) Fix rdb check when performed on preamble AOF tests: run replication tests for diskless slave too make replication test a bit more aggressive Add test for diskless load swapdb
-
- 22 May, 2019 1 commit
-
-
Angus Pearson authored
Add tests to check basic functionality of this optional keyword, and also tested with a module (redisgraph). Checked quickly with valgrind, no issues. Copies name the type name canonicalisation code from `typeCommand`, perhaps this would be better factored out to prevent the two diverging and both needing to be edited to add new `OBJ_*` types, but this is a little fiddly with C strings. The [redis-doc](https://github.com/antirez/redis-doc/blob/master/commands.json) repo will need to be updated with this new arg if accepted. A quirk to be aware of here is that the GEO commands are backed by zsets not their own type, so they're not distinguishable from other zsets. Additionally, for sparse types this has the same behaviour as `MATCH` in that it may return many empty results before giving something, even for large `COUNT`s.
-
- 14 May, 2019 1 commit
-
-
antirez authored
In fast systems "SLOWLOG RESET" is fast enough to don't be logged even when the time limit is "1" sometimes. Leading to false positives such as: [err]: SLOWLOG - can be disabled in tests/unit/slowlog.tcl Expected '1' to be equal to '0'
-
- 13 May, 2019 1 commit
-
-
antirez authored
Now clients that are ready to be terminated asynchronously are processed more often in beforeSleep() instead of being processed in serverCron(). This means that the test will not be able to catch the moment the client was terminated, also note that the 'omem' figure now changes in big steps, because of the new client output buffers layout. So we have to change the test range in order to accomodate for that. Yet the test is useful enough to be worth taking, even if its precision is reduced by this commit. Probably if we get more problems, a thing that makes sense is just to check that the limit is < 200k. That's more than enough actually.
-
- 10 May, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 05 May, 2019 1 commit
-
-
Oran Agra authored
solving few replication related tests race conditions which fail on slow machines bugfix in slave buffers test: since the test is executed twice, each time with a different commands count, the threshold for the delta can't be a constant.
-
- 15 Apr, 2019 1 commit
-
-
antirez authored
-
- 08 Apr, 2019 2 commits
- 24 Mar, 2019 2 commits
-
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
- 21 Mar, 2019 2 commits
-
-
Yossi Gottlieb authored
Add a flag to automatically protect filters from being called recursively by their own module.
-
Yossi Gottlieb authored
A filter handle is returned and can be used to unregister a filter. In the future it can also be used to further configure or manipulate the filter. Filters are now automatically unregistered when a module unloads.
-
- 18 Mar, 2019 2 commits
-
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
- 15 Mar, 2019 2 commits
- 12 Mar, 2019 1 commit
-
-
Steve Webster authored
-
- 08 Mar, 2019 1 commit
-
-
Steve Webster authored
The XCLAIM docs state the XCLAIM increments the delivery counter for messages. This PR makes the code match the documentation - which seems like the desired behaviour - whilst still allowing RETRYCOUNT to be specified manually. My understanding of the way streamPropagateXCLAIM() works is that this change will safely propagate to replicas since retry count is pulled directly from the streamNACK struct. Fixes #5194
-
- 30 Jan, 2019 1 commit
-
-
antirez authored
-
- 28 Jan, 2019 7 commits
- 18 Jan, 2019 1 commit
-
-
antirez authored
-
- 17 Jan, 2019 1 commit
-
-
antirez authored
This way the behavior is very similar to the past one. This is useful in order to remember the user she probably failed to configure a password correctly.
-
- 15 Jan, 2019 1 commit
-
-
Madelyn Olson authored
-
- 12 Dec, 2018 1 commit
-
-
antirez authored
-
- 28 Nov, 2018 1 commit
-
-
Qu Chen authored
-
- 19 Nov, 2018 2 commits
- 12 Nov, 2018 1 commit
-
-
Oran Agra authored
-
- 17 Oct, 2018 1 commit
-
-
antirez authored
-
- 16 Oct, 2018 2 commits
-
-
zhaozhao.zz authored
-
antirez authored
See #5426.
-