summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* RDB: make RDB check aware of LFU/LRU opcodes.cgroupsantirez2018-03-151-9/+13
|
* RDB: LRU/LFU branches missed continue.antirez2018-03-151-0/+2
|
* RDB: Ability to load LFU/LRU info.antirez2018-03-151-19/+48
|
* RDB: Ability to save LFU/LRU info.antirez2018-03-152-6/+31
| | | | | | | | | | | | | | | | | | This is a big win for caching use cases, since on reloading Redis will still have some idea about what is worth to evict and what not. However this only solves part of the problem because the information is only partially propagated to slaves (on write operations). Reads will not affect slaves LFU and LRU counters, so after a failover the eviction decisions are kinda random until keys start to collect some aging/freq info. However since new slaves are initially populated via RDB file transfer, this means that if we spin up a new slave from a master, and perform an immediate manual failover (for instance in order to upgrade the master), the slave will have eviction informations to use for some time. The LFU/LRU info is persisted only if the maxmemory policy is set to one of the relevant type, even if no actual "maxmemory" memory limit is set.
* CG: XINFO STREAM.antirez2018-03-151-3/+29
|
* CG: XINFO GROUPS + output format changes.antirez2018-03-151-2/+31
| | | | | | | | | XINFO is mainly an observability command that will be used more by humans than computers, and even when used by computers it will be a very low traffic command. For this reason the format was changed in order to have field names. They'll consume some bandwidth and CPU cycles, but in this context this is much better than having to understand what the numbers in the output array are.
* CG: XINFO CONSUMERS implemented.antirez2018-03-153-0/+53
|
* Streams: fix XREAD missing check for NULL object.antirez2018-03-151-1/+1
|
* CG: throw an error if XREADGROUP is used without GROUP.antirez2018-03-151-0/+7
|
* CG: XGROUP DELCONSUMER implemented.antirez2018-03-151-1/+46
|
* CG: remove stale comment. XREADGROUP is now implemented.antirez2018-03-151-2/+0
|
* CG: implement RETRYCOUNT in XCLAIM.antirez2018-03-151-0/+2
|
* CG: fix CG RDB loading not found conditional.antirez2018-03-151-1/+1
|
* CG: NACK created by XCLAIM FORCE must be set in global PEL.antirez2018-03-151-0/+1
|
* CG: implement XCLAIM FORCE option.antirez2018-03-151-3/+28
|
* CG: XCLAIM now updates the idle time of the message.antirez2018-03-153-8/+18
|
* Streams: trap more errors in stream loading + RDB check type name.antirez2018-03-152-1/+10
|
* CG: XCLAIM, use minidle and fix array len.antirez2018-03-151-4/+18
|
* CG: remove unused argument from streamReplyWithRangeFromConsumerPEL().antirez2018-03-151-3/+3
|
* CG: fix RDB saving when there are no consumer groups.antirez2018-03-151-21/+25
|
* Streams: fix error description for XADD when specified ID is small.antirez2018-03-151-1/+1
|
* CG: XCLAIM initial draft.antirez2018-03-151-3/+163
|
* Make addReplyError...() family functions able to get error codes.antirez2018-03-151-1/+11
| | | | | | | | | Now you can use: addReplyError("-MYERRORCODE some message"); If the error code is omitted, the behavior is like in the past, the generic -ERR will be used.
* CG: test XACK remaining features.antirez2018-03-151-0/+10
|
* CG: test XACK ability to remove items from the PELs.antirez2018-03-151-0/+13
|
* CG: test XPENDING ability to return pending items.antirez2018-03-151-0/+20
|
* CG: test XGROUPREAD abilities.antirez2018-03-151-0/+30
|
* CG: test group creation.antirez2018-03-151-0/+1
|
* CG: More specific duplicated group error.antirez2018-03-152-1/+13
|
* CG: RDB loading, fix inverted conditional.antirez2018-03-151-1/+1
|
* CG: RDB loading first implementation.antirez2018-03-153-9/+88
|
* CG: RDB saving part 2, consumers.antirez2018-03-151-1/+41
|
* CG: RDB saving part 1, metadata and PEL.antirez2018-03-151-1/+73
|
* CG: XPENDING should not create consumers and obey to count.antirez2018-03-153-6/+15
|
* CG: XPENDING with start/stop/count variant implemented.antirez2018-03-151-3/+55
|
* CG: XPENDING without start/stop variant implemented.antirez2018-03-153-1/+79
|
* CG: Now XREADGROUP + blocking operations work.antirez2018-03-153-8/+42
|
* CG: XACK should return zero when nothing is processed.antirez2018-03-151-1/+1
|
* CG: XACK implementation.antirez2018-03-153-4/+56
|
* CG: XREADGROUP can fetch data from the consumer PEL.antirez2018-03-151-14/+25
|
* CG: first draft of streamReplyWithRangeFromConsumerPEL().antirez2018-03-152-22/+81
|
* CG: Fix order of calls in streamReplyWithRange().antirez2018-03-151-1/+2
| | | | | We need to check if we are going to serve the request via the PEL before inserting a deferred array len in the client output buffer.
* CG: creation of NACK entries in PELs.antirez2018-03-153-24/+75
|
* CG: fix XREADGROUP ">" special ID parsing due to missing "continue".antirez2018-03-151-0/+1
|
* CG: streamCompareID() + group last_id updating.antirez2018-03-151-4/+33
|
* CG: consumer lookup + initial streamReplyWithRange() work to supprot CG.antirez2018-03-153-8/+44
|
* CG: add & populate group+consumer in the blocking state.antirez2018-03-154-8/+13
|
* CG: fix parsing in XREADGROUP and streamLookupCG() NULL check.antirez2018-03-151-2/+3
|
* CG: add XREADGROUP in the command table.antirez2018-03-151-0/+1
|
* CG: XGROUPREAD group option parsing and groups lookup.antirez2018-03-152-8/+66
|
View Lorry Controller Status