summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* server.current_client fix and minor refactoring.current-client-fixantirez2015-02-262-17/+11
| | | | Related to issue #2409.
* Improvements to PR #2425antirez2015-02-261-10/+10
| | | | | | | | 1. Remove useless "cs" initialization. 2. Add a "select" var to capture a condition checked multiple times. 3. Avoid duplication of the same if (!copy) conditional. 4. Don't increment dirty if copy is given (no deletion is performed), otherwise we propagate MIGRATE when not needed.
* Add last_dbid to migrateCachedSocket to avoid redundant SELECTTommy Wang2015-02-261-23/+36
| | | | | Avoid redundant SELECT calls when continuously migrating keys to the same dbid within a target Redis instance.
* utils/hashtable/rehashing.c test updated to use new API.antirez2015-02-251-12/+22
|
* Merge pull request #2405 from sisirkoppaka/unstableSalvatore Sanfilippo2015-02-251-1/+1
|\ | | | | rehashing.c: Fix compile error originating from SPOP rewrite
| * rehashing.c: Fix compile error originating from SPOP rewriteSisir Koppaka2015-02-181-1/+1
| |
* | Test: fixes a few tests after basic unit refactoring.antirez2015-02-251-2/+4
| |
* | Cast sentlen to int before comparison wit bufpos.antirez2015-02-251-1/+1
| | | | | | | | | | This is safe since bufpos is small, inside the range of the local client buffer.
* | Test: split basic unit into string, incr, keyspace units.antirez2015-02-254-399/+400
| |
* | Merge pull request #2050 from mattsta/bitops-no-overallocSalvatore Sanfilippo2015-02-252-6/+4
|\ \ | | | | | | Bitops: Stop overallocating storage space on set
| * | Bitops: Stop overallocating storage space on setMatt Stancliff2014-12-112-6/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously the string was created empty then re-sized to fit the offset, but sds resize causes the sds to over-allocate by at least 1 MB (which is a lot when you are operating at bit-level access). This also improves the speed of initial sets by 2% to 6% based on quick testing. Patch logic provided by @oranagra Fixes #1918
* | | Merge pull request #2054 from mattsta/fix-set-sentinel-quorumSalvatore Sanfilippo2015-02-251-0/+6
|\ \ \ | | | | | | | | Sentinel: Add initial quorum bounds check
| * | | Sentinel: Add initial quorum bounds checkMatt Stancliff2014-11-201-0/+6
| | | | | | | | | | | | | | | | Fixes #2054
* | | | Fix types broken by previous type cleanupMatt Stancliff2015-02-241-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | Revert some size_t back to off_t Set reply_bytes needs to 64 bits everywhere Revert bufpos to int since it's a max of 16k into buf[]
* | | | Merge pull request #2301 from mattsta/fix/lengthsSalvatore Sanfilippo2015-02-248-30/+30
|\ \ \ \ | | | | | | | | | | Improve type correctness
| * | | | Improve networking type correctnessMatt Stancliff2015-01-195-12/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | read() and write() return ssize_t (signed long), not int. For other offsets, we can use the unsigned size_t type instead of a signed offset (since our replication offsets and buffer positions are never negative).
| * | | | Improve RDB type correctnessMatt Stancliff2015-01-193-18/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's possible large objects could be larger than 'int', so let's upgrade all size counters to ssize_t. This also fixes rdbSaveObject serialized bytes calculation. Since entire serializations of data structures can be large, so we don't want to limit their calculated size to a 32 bit signed max. This commit increases object size calculation and cascades the change back up to serializedlength printing. Before: 127.0.0.1:6379> debug object hihihi ... encoding:quicklist serializedlength:-2147483559 ... After: 127.0.0.1:6379> debug object hihihi ... encoding:quicklist serializedlength:2147483737 ...
* | | | | Merge pull request #1966 from mattsta/fix-sentinel-infoSalvatore Sanfilippo2015-02-241-7/+13
|\ \ \ \ \ | | | | | | | | | | | | Sentinel: Improve INFO command behavior
| * | | | | Sentinel: Improve INFO command behaviorMatt Stancliff2014-12-111-7/+13
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improvements: - Return empty string if asking for non-existing section (INFO foo) - Fix potential memory leak (caused by sdsempty() then returned if >2 args) - Clean up argument parsing - Allow "all" as valid section (same as "default" or zero args currently) - Move strcasecmp to end of evaluation chain in conditionals Also, since we're C99, I moved some variable declarations to be closer to where they are actually used (saves us from needing to free an empty info if detect argument errors up front). Closes #1915 Closes #1966
* | | | | Merge pull request #2273 from mattsta/improve/consistency/INFO/memorySalvatore Sanfilippo2015-02-241-5/+20
|\ \ \ \ \ | | | | | | | | | | | | Improve consistency of INFO MEMORY
| * | | | | Add maxmemory limit to INFO MEMORYMatt Stancliff2015-01-091-4/+10
| | | | | | | | | | | | | | | | | | | | | | | | Since we have the eviction policy, we should have the memory limit too.
| * | | | | Improve consistency of INFO MEMORY fieldsMatt Stancliff2015-01-091-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds used_memory_rss_human and used_memory_lua_human to match all the other fields reporting human-readable memory too.
* | | | | | Merge pull request #2401 from mattsta/fix/quicklist/popSalvatore Sanfilippo2015-02-241-2/+13
|\ \ \ \ \ \ | | | | | | | | | | | | | | Fix quicklist Pop()
| * | | | | | Fix quicklist tests for Pop()Matt Stancliff2015-02-171-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now the tests actually compare return values instead of just verifying _something_ got returned.
| * | | | | | Fix quicklist Pop() resultJohn Doe2015-02-171-1/+1
| | |_|_|_|/ | |/| | | | | | | | | | | | | | | | Closes #2398
* | | | | | Change RENAME behavior when src and dst keys are the same.antirez2015-02-232-6/+21
| | | | | | | | | | | | | | | | | | | | | | | | Fixes issue #2392.
* | | | | | Give obvious instructions on how to bind all interfaces.antirez2015-02-191-0/+3
| | | | | |
* | | | | | Example redis.conf binds just to 127.0.0.1.antirez2015-02-191-28/+42
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's hard to pick a good approach here. A few arguments: 1) There are many exposed instances on the internet. 2) Changing the default when "bind" is not given is very dangerous, after an upgrade the server changes a fundamental behavior. 3) Usually Redis, when used in a proper way, will be protected *and* accessed often from other computers, so this new default is likely not what most people want. 4) However if users end with this default, they are using the example redis.conf: likely they are reading what is inside, and they'll see the warning.
* | | | | Merge branch 'unstable' of github.com:/antirez/redis into unstableantirez2015-02-141-10/+13
|\ \ \ \ \
| * \ \ \ \ Merge pull request #2393 from badboy/readme-fixSalvatore Sanfilippo2015-02-131-10/+13
| |\ \ \ \ \ | | | | | | | | | | | | | | Readme fix
| | * | | | | Link files in READMEJan-Erik Rediger2015-02-131-2/+5
| | | | | | |
| | * | | | | Use code tags where necessary, escape special markersJan-Erik Rediger2015-02-131-8/+8
| | | | | | |
* | | | | | | Version bumped to 3.1.999 (3.2 alpha versions).antirez2015-02-141-1/+1
|/ / / / / /
* | | | | | Fix README links again.antirez2015-02-131-9/+4
| | | | | | | | | | | | | | | | | | | | | | | | Apparently no refernece-style links supported in Github markdown.
* | | | | | Fix links into README.Salvatore Sanfilippo2015-02-131-4/+4
| | | | | |
* | | | | | README: give idea about what Redis is.antirez2015-02-131-0/+25
|/ / / / /
* | | | | A few more README markdown conversions.antirez2015-02-131-3/+3
| | | | |
* | | | | Fix README minor grammar issues.antirez2015-02-131-1/+1
| | | | |
* | | | | README -> README.md.antirez2015-02-131-13/+8
| | | | |
* | | | | redis-cli --latency-dist: one gray more, and --mono support.antirez2015-02-131-7/+17
| | | | |
* | | | | redis-cli --latency-dist, hopefully better palette.antirez2015-02-131-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Less grays: more readable palette since usually we have a non linear distribution of percentages and very near gray tones are hard to take apart. Final part of the palette is gradient from yellow to red. The red part is hardly reached because of usual distribution of latencies, but shows up mainly when latencies are very high because of the logarithmic scale, this is coherent to what people expect: red = bad.
* | | | | Merge pull request #2390 from sawaman/fix-typoSalvatore Sanfilippo2015-02-121-1/+1
|\ \ \ \ \ | | | | | | | | | | | | Unify to uppercase the headline
| * | | | | Unify to uppercase the headlineMasahiko Sawada2015-02-121-1/+1
| | | | | |
* | | | | | Extend memory unit support in CONFIG SET.antirez2015-02-121-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | Related to PR #2357.
* | | | | | Merge pull request #2357 from lamby/config-set-maxmemory-unitsSalvatore Sanfilippo2015-02-121-2/+3
|\ \ \ \ \ \ | | | | | | | | | | | | | | Support "1G" etc. units in CONFIG SET maxmemory
| * | | | | | Support "1G" etc. units in CONFIG SET maxmemoryChris Lamb2015-02-041-2/+3
| | |_|_|/ / | |/| | | | | | | | | | | | | | | | Signed-off-by: Chris Lamb <chris@chris-lamb.co.uk>
* | | | | | Better memtoll() error checking.antirez2015-02-121-5/+18
| |/ / / / |/| | | | | | | | | | | | | | Related to PR #2357.
* | | | | SPOP replication tests.antirez2015-02-111-0/+19
| | | | |
* | | | | SPOP explicit tests for the three different code paths.antirez2015-02-111-0/+27
| | | | |
* | | | | SPOP with count: fix replication for code path #3.antirez2015-02-111-2/+10
| | | | |
View Lorry Controller Status