Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Now Lua scripts dispatch Redis commands properly calling the call() ↵ | antirez | 2012-02-02 | 4 | -16/+34 |
| | | | | function. In order to make this possible call() was improved with a new flags argument that controls how the Redis command is executed. | ||||
* | Set a 3.5 GB maxmemory limit with noeviction policy if a 32 bit instance ↵ | antirez | 2012-02-02 | 1 | -0/+10 |
| | | | | without user-provided memory limits is detected. | ||||
* | Added a server.arch_bits field instead of computing it at runtime for INFO. | antirez | 2012-02-02 | 2 | -2/+4 |
| | |||||
* | Only incremnet stats for key miss/hit when the key is semantically accessed ↵ | antirez | 2012-02-01 | 1 | -3/+8 |
| | | | | in read-only. | ||||
* | Make SORT BY <constant> STORE ... to always produce the same output by force ↵ | antirez | 2012-02-01 | 1 | -0/+9 |
| | | | | sorting, so that we have deterministic replication of this command. | ||||
* | SORT is now more deterministic: does not accept to compare by score items ↵ | antirez | 2012-02-01 | 4 | -6/+51 |
| | | | | that have scores not representing a valid double. Also items with the same score are compared lexycographically. At the same time the scripting side introduced the ability to sort the output of SORT when sort uses the BY <constant> optimization, resulting in no specific ordering. Since in this case the user may use GET, and the result of GET can be null, converted into false as Lua data type, this commit also introduces the ability to sort Lua tables containining false, only if the first (faster) attempt at using just table.sort with a single argument fails. | ||||
* | Order output of commands returning random arrays using table.sort when ↵ | antirez | 2012-01-31 | 3 | -9/+36 |
| | | | | called from Lua, partially fixing issue #165. The issue is yet not completely fixed since we can't add the REDIS_CMD_SORT_FOR_SCRIPT flag in SORT currently, both because it may contain NULLs and because it is not cool to re-sort everything at every call when instead this should be sorted only if BY <constant> is used. | ||||
* | Fixed redis-benchmark --help output typo | antirez | 2012-01-31 | 1 | -2/+4 |
| | |||||
* | 64 bit instances are no longer limited to have at max 2^32-1 elements in lists. | antirez | 2012-01-31 | 5 | -18/+12 |
| | |||||
* | Merge remote-tracking branch 'origin/unstable' into unstable | antirez | 2012-01-30 | 1 | -2/+2 |
|\ | |||||
| * | Merge pull request #319 from fawek/lua-error-location | Salvatore Sanfilippo | 2012-01-30 | 1 | -2/+2 |
| |\ | | | | | | | Lua reports line numbers off by one in error messages | ||||
| | * | Lua reports line numbers off by one in error messages | Jakub Wieczorek | 2012-01-29 | 1 | -2/+2 |
| | | | |||||
* | | | setKey(): call the higher level wrapper setModifiedKey() instead of ↵ | antirez | 2012-01-30 | 1 | -1/+1 |
|/ / | | | | | | | touchWatchedKey() even if currently they are exactly the same. | ||||
* | | SORT with STORE removes key if result is empty. This fixes issue #227. | Michal Kwiatkowski | 2012-01-30 | 1 | -2/+7 |
|/ | |||||
* | Fixed typo in getClientLimitClassByName() | antirez | 2012-01-25 | 1 | -1/+1 |
| | |||||
* | Fixed another possible bug in cluster.c found by clang --analyze. | antirez | 2012-01-25 | 1 | -1/+1 |
| | |||||
* | Merge branch 'unstable' into limits | antirez | 2012-01-25 | 1 | -1/+1 |
|\ | |||||
| * | Fixed a non critical bug signaled by clang static analyzer thanks to Mukund ↵ | antirez | 2012-01-25 | 1 | -1/+1 |
| | | | | | | | | Sivaraman for reporting it: there was a not initialized field populating the cluster message header, but it is always fixed at later time before sending the packet. | ||||
* | | Merge branch 'unstable' into limits | antirez | 2012-01-25 | 1 | -13/+11 |
|\ \ | |/ | |||||
| * | aeCreateEventLoop() cleanup on error unified in a single block (original | antirez | 2012-01-25 | 1 | -15/+11 |
| | | | | | | | | | | patch by Mukund Sivaraman, modified by me to make it simpler and to use my coding style). | ||||
| * | If aeApiCreate() fails, there's probably not much one can do, but in the ↵ | Mukund Sivaraman | 2012-01-25 | 1 | -0/+2 |
| | | | | | | | | name of consistency... | ||||
* | | lenght -> length | antirez | 2012-01-24 | 2 | -2/+2 |
| | | |||||
* | | after all closing a client for output buffer limit overcoming is a WARNING ↵ | antirez | 2012-01-24 | 1 | -1/+1 |
| | | | | | | | | level message. | ||||
* | | client-output-buffer-limit documented in redis.conf | antirez | 2012-01-24 | 1 | -4/+4 |
| | | |||||
* | | Client output buffer limits: configuration of parameters for the different ↵ | antirez | 2012-01-24 | 3 | -2/+106 |
| | | | | | | | | classes of clients implemented. | ||||
* | | asyncCloseClientOnOutputBufferLimitReached() now ignores clients with ↵ | antirez | 2012-01-24 | 2 | -8/+6 |
| | | | | | | | | REDIS_CLOSE_ASAP flag already set. Return value of the function changed from int to void since it is not used. Fixed logging of the client scheduled to be closed. | ||||
* | | client buffer handling refactoring and optimization | antirez | 2012-01-23 | 1 | -23/+47 |
| | | |||||
* | | actually call the function to async free clients in serverCron(). | antirez | 2012-01-23 | 1 | -0/+3 |
| | | |||||
* | | Implementation of the internals that make possible to terminate clients ↵ | antirez | 2012-01-23 | 4 | -0/+122 |
| | | | | | | | | overcoming configured output buffer (soft and hard) limits. | ||||
* | | Merge branch 'unstable' into limits | antirez | 2012-01-23 | 5 | -140/+296 |
|\ \ | |/ | |||||
| * | fixed typo in hahs function seed default value. It is no longer used but ↵ | antirez | 2012-01-22 | 1 | -1/+1 |
| | | | | | | | | fixed to retain the old constant as default anyway. | ||||
| * | typo in comment fixed | antirez | 2012-01-21 | 1 | -1/+1 |
| | | |||||
| * | Fix for hash table collision attack. We simply randomize hash table ↵ | antirez | 2012-01-21 | 4 | -4/+22 |
| | | | | | | | | initialization value at startup time. | ||||
| * | Better looking registers/stack dump | antirez | 2012-01-20 | 1 | -19/+22 |
| | | |||||
| * | added support to dump registers on crash on Linux x32 | antirez | 2012-01-20 | 1 | -1/+24 |
| | | |||||
| * | added support to dump registers on crash on Linux x64 | antirez | 2012-01-20 | 2 | -1/+29 |
| | | |||||
| * | all the stack trace related functions are now in debug.c. Now Redis dumps ↵ | antirez | 2012-01-20 | 3 | -136/+220 |
| | | | | | | | | registers and stack content on crash. Currently osx supported, adding Linux right now. | ||||
* | | Introduced three client limit classes: normal, slave, pubsub | antirez | 2012-01-17 | 2 | -0/+21 |
| | | |||||
* | | Track the length of the client pending output buffers (still to transfer) in ↵ | antirez | 2012-01-17 | 3 | -1/+31 |
|/ | | | | a new field in the client structure. | ||||
* | It is now posible to flush all the previous saving points in redis.conf by ↵ | antirez | 2012-01-16 | 1 | -6/+10 |
| | | | | using a save directive with a single empty string argument, like it happens for CONFIG SET save. | ||||
* | Don't change the replication state if SLAVE OF is called with arguments ↵ | antirez | 2012-01-16 | 1 | -1/+15 |
| | | | | specifying the same master we are already connected with. This fixes issues #290. | ||||
* | Obsolete SDS_ABORT_ON_OOM removed from sds.c | antirez | 2012-01-16 | 1 | -52/+3 |
| | |||||
* | sds.c no longe pre-allocate more than 1MB of free space ahead. This fixes ↵ | antirez | 2012-01-16 | 2 | -1/+7 |
| | | | | issue #252. | ||||
* | added a comment on top of the zslRandomLevel() function | antirez | 2012-01-16 | 1 | -0/+4 |
| | |||||
* | On crash print information about the current client (if any), command ↵ | antirez | 2012-01-12 | 4 | -4/+64 |
| | | | | vector, and object associated to first argument assuming it is a key. | ||||
* | error in comment fixed | antirez | 2012-01-11 | 1 | -1/+1 |
| | |||||
* | show GCC version in INFO output. | antirez | 2012-01-10 | 1 | -0/+6 |
| | |||||
* | version bumped to 2.9.3 | antirez | 2012-01-07 | 1 | -1/+1 |
| | |||||
* | Protections against protocol desyncs, leading to infinite query buffer ↵ | antirez | 2011-12-31 | 2 | -6/+24 |
| | | | | growing, due to nul-terms in specific bytes of the request or indefinitely long multi bulk or bulk count strings without newlines. This bug is related to Issue #141 as well. | ||||
* | Protocol and I/O related defines moved into a separated section of redis.h | antirez | 2011-12-31 | 1 | -4/+6 |
| |