antirez
0c4a8532c6
CG: XCLAIM now updates the idle time of the message.
2018-03-15 12:54:10 +01:00
antirez
4c1db9b9e7
Streams: trap more errors in stream loading + RDB check type name.
2018-03-15 12:54:10 +01:00
antirez
bebd33993c
CG: XCLAIM, use minidle and fix array len.
2018-03-15 12:54:10 +01:00
antirez
106eb6adcc
CG: remove unused argument from streamReplyWithRangeFromConsumerPEL().
2018-03-15 12:54:10 +01:00
antirez
3ecf2a1005
CG: fix RDB saving when there are no consumer groups.
2018-03-15 12:54:10 +01:00
antirez
fe9a0b9d6d
Streams: fix error description for XADD when specified ID is small.
2018-03-15 12:54:10 +01:00
antirez
d3c15ef886
CG: XCLAIM initial draft.
2018-03-15 12:54:10 +01:00
antirez
535c016ddf
Make addReplyError...() family functions able to get error codes.
...
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.
2018-03-15 12:54:10 +01:00
antirez
72282c440b
CG: test XACK remaining features.
2018-03-15 12:54:10 +01:00
antirez
c72389ef0f
CG: test XACK ability to remove items from the PELs.
2018-03-15 12:54:10 +01:00
antirez
862c29fc1b
CG: test XPENDING ability to return pending items.
2018-03-15 12:54:10 +01:00
antirez
0a5272cea8
CG: test XGROUPREAD abilities.
2018-03-15 12:54:10 +01:00
antirez
b3ae33b2ad
CG: test group creation.
2018-03-15 12:54:10 +01:00
antirez
8d3c0e4186
CG: More specific duplicated group error.
2018-03-15 12:54:10 +01:00
antirez
bd4dd842ea
CG: RDB loading, fix inverted conditional.
2018-03-15 12:54:10 +01:00
antirez
f979275a2a
CG: RDB loading first implementation.
2018-03-15 12:54:10 +01:00
antirez
80da510011
CG: RDB saving part 2, consumers.
2018-03-15 12:54:10 +01:00
antirez
9a686b82cd
CG: RDB saving part 1, metadata and PEL.
2018-03-15 12:54:10 +01:00
antirez
922b74828b
CG: XPENDING should not create consumers and obey to count.
2018-03-15 12:54:10 +01:00
antirez
c139073709
CG: XPENDING with start/stop/count variant implemented.
2018-03-15 12:54:10 +01:00
antirez
a85f0fc571
CG: XPENDING without start/stop variant implemented.
2018-03-15 12:54:10 +01:00
antirez
f49cbaf84c
CG: Now XREADGROUP + blocking operations work.
2018-03-15 12:54:10 +01:00
antirez
55b705689f
CG: XACK should return zero when nothing is processed.
2018-03-15 12:54:10 +01:00
antirez
9b2223cebd
CG: XACK implementation.
2018-03-15 12:54:10 +01:00
antirez
d82968ece2
CG: XREADGROUP can fetch data from the consumer PEL.
2018-03-15 12:54:10 +01:00
antirez
018f8a3c1d
CG: first draft of streamReplyWithRangeFromConsumerPEL().
2018-03-15 12:54:10 +01:00
antirez
391e1082a4
CG: Fix order of calls in streamReplyWithRange().
...
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.
2018-03-15 12:54:10 +01:00
antirez
840ad8cec6
CG: creation of NACK entries in PELs.
2018-03-15 12:54:10 +01:00
antirez
28d36e3aa3
CG: fix XREADGROUP ">" special ID parsing due to missing "continue".
2018-03-15 12:54:10 +01:00
antirez
e0733ff7f8
CG: streamCompareID() + group last_id updating.
2018-03-15 12:54:10 +01:00
antirez
0f43a908f9
CG: consumer lookup + initial streamReplyWithRange() work to supprot CG.
2018-03-15 12:54:10 +01:00
antirez
23dc98ac52
CG: add & populate group+consumer in the blocking state.
2018-03-15 12:54:10 +01:00
antirez
20bc183ef8
CG: fix parsing in XREADGROUP and streamLookupCG() NULL check.
2018-03-15 12:54:10 +01:00
antirez
ffedba44e5
CG: add XREADGROUP in the command table.
2018-03-15 12:54:10 +01:00
antirez
d293a8a11e
CG: XGROUPREAD group option parsing and groups lookup.
2018-03-15 12:54:10 +01:00
antirez
7dba47a535
CG: fix raxFind() retval check in streamCreateCG().
2018-03-15 12:54:10 +01:00
antirez
2c348dafd0
CG: data structures design + XGROUP CREATE implementation.
2018-03-15 12:54:10 +01:00
antirez
054a935d2c
Cluster: add test for the nofailover flag.
2018-03-14 16:30:32 +01:00
antirez
b94379e29a
Cluster: ability to prevent slaves from failing over their masters.
...
This commit, in some parts derived from PR #3041 which is no longer
possible to merge (because the user deleted the original branch),
implements the ability of slaves to have a special configuration
preventing that they try to start a failover when the master is failing.
There are multiple reasons for wanting this, and the feautre was
requested in issue #3021 time ago.
The differences between this patch and the original PR are the
following:
1. The flag is saved/loaded on the nodes configuration.
2. The 'myself' node is now flag-aware, the flag is updated as needed
when the configuration is changed via CONFIG SET.
3. The flag name uses NOFAILOVER instead of NO_FAILOVER to be consistent
with existing NOADDR.
4. The redis.conf documentation was rewritten.
Thanks to @deep011 for the original patch.
2018-03-14 14:01:38 +01:00
antirez
4ee8d1377f
Stream: update the listpack pointer in streamTrimByLength().
2018-03-01 17:26:02 +01:00
antirez
b4e6961fec
Remove warning from lpGet snprintf().
2018-03-01 15:26:27 +01:00
antirez
5db00d9547
redis-cli: fix missed unit in array. Change define name.
2018-03-01 15:06:41 +01:00
Salvatore Sanfilippo
aa1871bc5c
Merge pull request #4714 from charsyam/feature/fix-out-of-index-range
...
[BugFix] Fix out of array index range for findBigKeys in redis-cli
2018-03-01 03:39:15 -08:00
antirez
e5eafbc776
Actually use ae_flags to add AE_BARRIER if needed.
...
Many thanks to @Plasma that spotted this problem reviewing the code.
2018-02-28 18:03:51 +01:00
Salvatore Sanfilippo
c2d54c26df
Merge pull request #4715 from charsyam/feature/refactoring-make-condition-clear-for-rdb
...
[BugFix] fix calculation length in rdbSaveAuxField
2018-02-27 10:15:27 -08:00
antirez
7ba754281f
expireIfNeeded() needed a top comment documenting the behavior.
2018-02-27 16:44:43 +01:00
antirez
f7f696f4ae
expireIfNeeded() comment: claim -> pretend.
2018-02-27 16:37:37 +01:00
charsyam
4529e3dffa
refactoring-make-condition-clear-for-rdb
2018-02-27 21:55:20 +09:00
charsyam
fdea7d8cda
fix-out-of-index-range-for-redis-cli-findbigkey
2018-02-27 21:46:19 +09:00
antirez
7874da180e
ae.c: insetad of not firing, on AE_BARRIER invert the sequence.
...
AE_BARRIER was implemented like:
- Fire the readable event.
- Do not fire the writabel event if the readable fired.
However this may lead to the writable event to never be called if the
readable event is always fired. There is an alterantive, we can just
invert the sequence of the calls in case AE_BARRIER is set. This commit
does that.
2018-02-27 13:06:42 +01:00