- 13 7月, 2018 5 次提交
-
-
由 antirez 提交于
-
由 artix 提交于
-
由 artix 提交于
outputs a warning to the user.
-
由 artix 提交于
-
由 Salvatore Sanfilippo 提交于
Delete unused role checking.
-
- 12 7月, 2018 7 次提交
-
-
由 Shen Longxing 提交于
When check rdb file, it is unnecessary to check role.
-
由 Salvatore Sanfilippo 提交于
Remove unnecessary return statements
-
由 antirez 提交于
-
由 antirez 提交于
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 提交于
We don't really need to distinguish between the case the consumer is the same or is a different one.
-
由 Salvatore Sanfilippo 提交于
Streams: fix xreadgroup crash after xgroup SETID is sent.
-
由 Salvatore Sanfilippo 提交于
Active defrag fixes for 32bit builds (again)
-
- 11 7月, 2018 1 次提交
-
-
由 Oran Agra 提交于
* overflow in jemalloc fragmentation hint to the defragger
-
- 10 7月, 2018 9 次提交
-
-
由 Salvatore Sanfilippo 提交于
fix repeat argument issue and reduce unnessary loop times for redis-cli.
-
由 tengfeng 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
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 提交于
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 提交于
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 提交于
For issue #5111.
-
- 09 7月, 2018 9 次提交
-
-
由 Salvatore Sanfilippo 提交于
Fix indentation.
-
由 dejun.xdj 提交于
Save NOACK option into client.blockingState structure.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
We need CC_QUIET in order to fix #5096 by silently failing if needed.
-
由 Amit Dey 提交于
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 提交于
-
由 minkikim89 提交于
-
由 WuYunlong 提交于
-
- 04 7月, 2018 9 次提交