- 13 Jul, 2018 2 commits
- 12 Jul, 2018 7 commits
-
-
Salvatore Sanfilippo authored
Delete unused role checking.
-
Shen Longxing authored
When check rdb file, it is unnecessary to check role.
-
Salvatore Sanfilippo authored
Remove unnecessary return statements
-
antirez authored
-
antirez authored
We don't want to increment the deliveries here, because the sysadmin reset the consumer group so the desire is likely to restart processing, and having the PEL polluted with old information is not useful but probably confusing. Related to #5111.
-
antirez authored
We don't really need to distinguish between the case the consumer is the same or is a different one.
-
Salvatore Sanfilippo authored
Streams: fix xreadgroup crash after xgroup SETID is sent.
-
- 11 Jul, 2018 2 commits
-
-
Salvatore Sanfilippo authored
Active defrag fixes for 32bit builds (again)
-
Oran Agra authored
* overflow in jemalloc fragmentation hint to the defragger
-
- 10 Jul, 2018 9 commits
-
-
Salvatore Sanfilippo authored
fix repeat argument issue and reduce unnessary loop times for redis-cli.
-
tengfeng authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
To simplify the semantics of blocking for a group, this commit changes the implementation to better match the description we provide of conusmer groups: blocking for > will make the consumer waiting for new elements in the group. However blocking for any other ID will always serve the local history of the consumer. However it must be noted that the > ID is actually an alias for the special ID ms/seq of UINT64_MAX,UINT64_MAX.
-
antirez authored
To detect when the group (or the whole key) is destroyed to send an error to the consumers blocked in such group is a problem, so we leave the consumers listening, the sysadmin is free to create or destroy groups assuming she/he knows what to do. However a client may be blocked in a given consumer group, that is later destroyed. Then the stream receives new elements. In that case there is no sane behavior to serve the consumer... but to report an error about the group no longer existing. More about detecting this synchronously and why it is not done: 1. Normally we don't do that, we leave clients blocked for other data types such as lists. 2. When we free a stream object there is no longer information about what was the key it was associated with, so while destroying the consumer groups we miss the info to unblock the clients in that moment. 3. Objects can be reclaimed in other threads where it is no longer safe to do client operations.
-
antirez authored
When a client blocks for a consumer group, we don't know the actual ID we want to be served: other clients blocked in the same consumer group may be served first, so the consumer group latest delivered ID changes. This was not handled correctly, all the clients in the consumer group were unblocked without data but the first.
-
dejun.xdj authored
For issue #5111.
-
- 09 Jul, 2018 9 commits
-
-
Salvatore Sanfilippo authored
Fix indentation.
-
dejun.xdj authored
Save NOACK option into client.blockingState structure.
-
antirez authored
-
antirez authored
-
antirez authored
We need CC_QUIET in order to fix #5096 by silently failing if needed.
-
Amit Dey authored
http://help.github.com/send-pull-requests/ is no longer supported this change modifies the link to the working one https://help.github.com/articles/creating-a-pull-request/
-
dejun.xdj authored
-
minkikim89 authored
-
WuYunlong authored
-
- 04 Jul, 2018 11 commits
-
-
antirez authored
-
antirez authored
With such information will be able to use a private localtime() implementation serverLog(), which does not use any locking and is both thread and fork() safe.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
dejun.xdj authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-