gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
5,130 Commits 1 Branch 0 Tags
Commit Graph

5130 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Matt Stancliff
92f3e19db7 Fix types broken by previous type cleanup 
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[]
 2015-02-24 17:39:59 +01:00
Salvatore Sanfilippo
de4eacd132 Merge pull request #2301 from mattsta/fix/lengths 
Improve type correctness
 2015-02-24 17:22:53 +01:00
Salvatore Sanfilippo
b2ffd67c91 Merge pull request #1966 from mattsta/fix-sentinel-info 
Sentinel: Improve INFO command behavior
 2015-02-24 17:20:09 +01:00
Salvatore Sanfilippo
813c1d300a Merge pull request #2273 from mattsta/improve/consistency/INFO/memory 
Improve consistency of INFO MEMORY
 2015-02-24 17:19:17 +01:00
Salvatore Sanfilippo
37238841e5 Merge pull request #2401 from mattsta/fix/quicklist/pop 
Fix quicklist Pop()
 2015-02-24 17:13:39 +01:00
antirez
fa8fcff3f0 Change RENAME behavior when src and dst keys are the same. 
Fixes issue #2392.
 2015-02-23 11:24:24 +01:00
Jason Roth
6cc1d51719 added a new hvstrlen command 
the hvstrlen command returns the length of a hash field value
 2015-02-21 15:01:18 +00:00
antirez
5977a25a94 Give obvious instructions on how to bind all interfaces. 2015-02-19 22:47:32 +01:00
antirez
487ab5d55b Example redis.conf binds just to 127.0.0.1. 
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.
 2015-02-19 22:42:31 +01:00
Sisir Koppaka
aa9b7743eb rehashing.c: Fix compile error originating from SPOP rewrite 2015-02-18 08:16:41 -05:00
Matt Stancliff
58061fe49b Fix quicklist tests for Pop() 
Now the tests actually compare return values instead of just
verifying _something_ got returned.
 2015-02-17 11:33:08 -05:00
John Doe
62a6895054 Fix quicklist Pop() result 
Closes #2398
 2015-02-17 11:31:08 -05:00
antirez
ae51d42ba8 Merge branch 'unstable' of github.com:/antirez/redis into unstable 2015-02-14 17:19:37 +01:00
antirez
7009630914 Version bumped to 3.1.999 (3.2 alpha versions). 2015-02-14 17:19:17 +01:00
Salvatore Sanfilippo
9793db8416 Merge pull request #2393 from badboy/readme-fix 
Readme fix
 2015-02-13 15:55:44 +01:00
Jan-Erik Rediger
836f168a48 Link files in README 2015-02-13 15:51:38 +01:00
antirez
8eb3a22245 Fix README links again. 
Apparently no refernece-style links supported in Github markdown.
 2015-02-13 15:39:44 +01:00
Salvatore Sanfilippo
f537d4d10e Fix links into README. 2015-02-13 15:37:19 +01:00
antirez
4689cba9ab README: give idea about what Redis is. 2015-02-13 15:34:22 +01:00
Jan-Erik Rediger
70e9735598 Use code tags where necessary, escape special markers 2015-02-13 15:10:20 +01:00
antirez
ad1bfa5a4d A few more README markdown conversions. 2015-02-13 14:57:08 +01:00
antirez
f634cb03ae Fix README minor grammar issues. 2015-02-13 14:55:53 +01:00
antirez
b2aeaaddc8 README -> README.md. 2015-02-13 14:55:09 +01:00
antirez
40f50b38e0 redis-cli --latency-dist: one gray more, and --mono support. 2015-02-13 14:38:21 +01:00
antirez
b0d3557307 redis-cli --latency-dist, hopefully better palette. 
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.
 2015-02-13 12:52:46 +01:00
Salvatore Sanfilippo
dec00755fe Merge pull request #2390 from sawaman/fix-typo 
Unify to uppercase the headline
 2015-02-12 17:07:04 +01:00
antirez
75a2dbffa8 Extend memory unit support in CONFIG SET. 
Related to PR #2357.
 2015-02-12 16:51:20 +01:00
Salvatore Sanfilippo
a4e2db7451 Merge pull request #2357 from lamby/config-set-maxmemory-units 
Support "1G" etc. units in CONFIG SET maxmemory
 2015-02-12 16:42:09 +01:00
antirez
07d4c76179 Better memtoll() error checking. 
Related to PR #2357.
 2015-02-12 16:40:46 +01:00
Masahiko Sawada
f3f936fb4c Unify to uppercase the headline 2015-02-12 21:20:22 +09:00
antirez
45a1c66553 SPOP replication tests. 2015-02-11 10:52:28 +01:00
antirez
b842565acb SPOP explicit tests for the three different code paths. 2015-02-11 10:52:28 +01:00
antirez
38000e913a SPOP with count: fix replication for code path #3. 2015-02-11 10:52:28 +01:00
antirez
87a6696d89 SPOP: reimplemented for speed and better distribution. 
The old version of SPOP with "count" argument used an API call of dict.c
which was actually designed for a different goal, and was not capable of
good distribution. We follow a different three-cases approach optimized
for different ratiion between sets and requested number of elements.

The implementation is simpler and allowed the removal of a large amount
of code.
 2015-02-11 10:52:28 +01:00
antirez
38afac7752 alsoPropagate: handle REDIS_CALL_PROPAGATE and AOF loading. 2015-02-11 10:52:28 +01:00
antirez
9bffc3f0c6 Change alsoPropagate() behavior to make it more usable. 
Now the API automatically creates its argv copy and increment ref count
of passed objects.
 2015-02-11 10:52:27 +01:00
antirez
54def17f37 SPOP with count: initial fixes to the implementation. 
Severan problems are addressed but still a few missing.
Since replication of this command was more complex than others since it
needs to replicate multiple SREM commands, an old API able to do this
was reused (it was taken inside the implementation since it was pretty
obvious soon or later that would be useful). The API was improved a bit
so that now a command may opt-out for the standard command replication
when the server.dirty counter is incremented, in order to "manually"
replicate what it wants.
 2015-02-11 10:52:27 +01:00
antirez
c752dc5adb Separate latency monitoring of eviction loop and eviction DELs. 2015-02-11 10:52:27 +01:00
antirez
e1da371706 dict.c: reset emptylen when bucket is not empty. 
Fixed by @oranagra, thank you.
 2015-02-11 10:52:27 +01:00
antirez
b153f6f2da dict.c Rehashing visualization code snippet added to utils. 2015-02-11 10:52:27 +01:00
antirez
33799b02ab redis-cli --stat: show LOAD when loading. 2015-02-11 10:52:27 +01:00
antirez
b139745a35 Remove optional single-key path from evictionPoolPopulate(). 2015-02-11 10:52:27 +01:00
antirez
2bb647770d dict.c: add dictGetSomeKeys(), specialized for eviction. 2015-02-11 10:52:27 +01:00
antirez
6086a3656a dict.c: avoid code repetition in dictRehash(). 
Avoid code repetition introduced with PR #2367, also fixes the return
value to always return 0 if there is nothing more to rehash.
 2015-02-11 10:52:27 +01:00
Sun He
9c047bbfec dict.c/dictRehash: check again to update 2015-02-11 10:52:26 +01:00
antirez
15940c1988 dict.c: don't try buckets that are empty for sure in dictGetRandomKey(). 
This is very similar to the optimization applied to dictGetRandomKeys,
but applied to the single key variant.

Related to issue #2306.
 2015-02-11 10:52:26 +01:00
antirez
5d106de0c9 dict.c: dictGetRandomKeys() optimization for big->small table case. 
Related to issue #2306.
 2015-02-11 10:52:26 +01:00
antirez
71b990a7ab dict.c: dictGetRandomKeys() visit pattern optimization. 
We use the invariant that the original table ht[0] is never populated up
to the index before the current rehashing index.

Related to issue #2306.
 2015-02-11 10:52:26 +01:00
antirez
19d51b181b dict.c: put a bound to max work dictRehash() call can do. 
Related to issue #2306.
 2015-02-11 10:52:26 +01:00
antirez
1115984e9f dict.c: prevent useless resize to same size. 
Related to issue #2306.
 2015-02-11 10:52:26 +01:00