- 22 Nov, 2019 5 commits
-
-
antirez authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
- 21 Nov, 2019 1 commit
-
-
antirez authored
-
- 20 Nov, 2019 1 commit
-
-
Madelyn Olson authored
-
- 19 Nov, 2019 7 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
Yossi Gottlieb authored
RM_Call() will now use EBADF and ENONET in addition to EINVAL in order to provide more information about errors (i.e. when return value is NULL).
-
antirez authored
-
喜欢兰花山丘 authored
fix date +%s errata
-
Daniel Dai authored
-
- 18 Nov, 2019 4 commits
- 15 Nov, 2019 2 commits
- 14 Nov, 2019 5 commits
-
-
antirez authored
-
antirez authored
-
Oran Agra authored
trimming talk about RESP protocol from API docs (should be independent to that anyway)
-
Oran Agra authored
-
Yossi Gottlieb authored
This is a light-weight replace function, useful for use cases such as realloc()ing an existing value, etc. Using RM_ModuleTypeSetValue() in such cases is wasteful and complex as it attempts to delete the old value, call its destructor, etc.
-
- 13 Nov, 2019 2 commits
-
-
Guy Benoish authored
Calling XADD with 0-0 or 0 would result in creating an empty key and storing it in the database. Even worse, because XADD will reply with error the action will not be replicated, creating a master-replica inconsistency
-
喜欢兰花山丘 authored
Update listGetFree keep format consistent
-
- 12 Nov, 2019 1 commit
-
-
Oran Agra authored
Reduce default minimum effort, so that when fragmentation is just detected, the impact on the latency will be minor. Reduce the default maximum effort, mainly to prevent a case were a sudden massive deletions, won't trigger an aggressive defrag that will cause latency. When activedefrag is disabled mid-run, reset the 'running' info field, and clear the scan cursor, so that when it'll be re-enabled, a new fresh scan will start. Clearing the 'running' variable is important since lowering the defragger tunables mid-scan won't help, the defragger only considers new threshold when a new scan starts, and during a scan it can only become more aggressive, (when more severe fragmentation is detected), it'll never go less aggressive. So by temporarily disabling activedefrag, one can lower th the tunables. Removing the experimantal warning.
-
- 11 Nov, 2019 3 commits
-
-
Oran Agra authored
- Adding RM_ScanKey - Adding tests for RM_ScanKey - Refactoring RM_Scan API Changes in RM_Scan - cleanup in docs and coding convention - Moving out of experimantal Api - Adding ctx to scan callback - Dont use cursor of -1 as an indication of done (can be a valid cursor) - Set errno when returning 0 for various reasons - Rename Cursor to ScanCursor - Test filters key that are not strings, and opens a key if NULL
-
meir@redislabs.com authored
The implementation expose the following new functions: 1. RedisModule_CursorCreate - allow to create a new cursor object for keys scanning 2. RedisModule_CursorRestart - restart an existing cursor to restart the scan 3. RedisModule_CursorDestroy - destroy an existing cursor 4. RedisModule_Scan - scan keys The RedisModule_Scan function gets a cursor object, a callback and void* (used as user private data). The callback will be called for each key in the database proving the key name and the value as RedisModuleKey.
-
David Carlier authored
-
- 10 Nov, 2019 1 commit
-
-
Oran Agra authored
- the API name was odd, separated to two apis one for LRU and one for LFU - the LRU idle time was in 1 second resolution, which might be ok for RDB and RESTORE, but i think modules may need higher resolution - adding tests for LFU and for handling maxmemory policy mismatch
-
- 08 Nov, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 07 Nov, 2019 1 commit
-
-
Patrick Valsecchi authored
When a redis instance becomes a slave, sentinel also kills pubsub clients. Closes #6545
-
- 06 Nov, 2019 6 commits
-
-
meir@redislabs.com authored
-
Guy Benoish authored
Fixes GitHub issue #6492 Added stream support in RM_KeyType and RM_ValueLength. Also moduleDelKeyIfEmpty was updated, even though it has no effect now (It will be relevant when stream type direct API will be coded - i.e. RM_StreamAdd)
-
meir@redislabs.com authored
-
meir@redislabs.com authored
-
meir@redislabs.com authored
The exposed functions: 1. RedisModule_GetUsedMemoryPercentage - return the used memory 2. RedisModue_MallocSize - return for a given pointer, the amount of memory allocated for this pointer
-
antirez authored
One problem with the solution proposed so far in #6537 is that key lookups outside a command execution via call(), still used a cached time. The cached time needed to be refreshed in multiple places, especially because of modules callbacks from timers, cluster bus, and thread safe contexts, that may use RM_Open(). In order to avoid this problem, this commit introduces the ability to detect if we are inside call(): this way we can use the reference fixed time only when we are in the context of a command execution or Lua script, but for the asynchronous lookups, we can still use mstime() to get a fresh time reference.
-