- 09 Aug, 2016 1 commit
-
-
antirez authored
-
- 27 Jul, 2016 1 commit
-
-
antirez authored
This feature is useful, especially in deployments using Sentinel in order to setup Redis HA, where the slave is executed with NAT or port forwarding, so that the auto-detected port/ip addresses, as listed in the "INFO replication" output of the master, or as provided by the "ROLE" command, don't match the real addresses at which the slave is reachable for connections.
-
- 20 Jul, 2016 1 commit
-
-
antirez authored
-
- 15 Jul, 2016 1 commit
-
-
antirez authored
Implementation of LFU maxmemory policy for anything related to Redis objects. Still no actual eviction implemented.
-
- 04 Jul, 2016 1 commit
-
-
antirez authored
Like CONFIG SET always was. Close #3369.
-
- 13 Jun, 2016 3 commits
- 05 Jun, 2016 2 commits
-
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
- 22 May, 2016 1 commit
-
-
oranagra authored
-
- 10 May, 2016 1 commit
-
-
antirez authored
-
- 04 May, 2016 1 commit
-
-
antirez authored
Thanks to @oranagra for the idea of allowing CONFIG GET during loading.
-
- 25 Apr, 2016 1 commit
-
-
Oran Agra authored
-
- 22 Apr, 2016 1 commit
-
-
therealbill authored
I've renamed maxmemoryToString to evictPolicyToString since that is more accurate (and easier to mentally connect with the correct data), as well as updated the function to user server.maxmemory_policy rather than server.maxmemory. Now with a default config it is actually returning the correct policy rather than volatile-lru.
-
- 29 Jan, 2016 2 commits
- 25 Jan, 2016 1 commit
-
-
antirez authored
-
- 07 Jan, 2016 1 commit
-
-
antirez authored
An exposed Redis instance on the internet can be cause of serious issues. Since Redis, by default, binds to all the interfaces, it is easy to forget an instance without any protection layer, for error. Protected mode try to address this feature in a soft way, providing a layer of protection, but giving clues to Redis users about why the server is not accepting connections. When protected mode is enabeld (the default), and if there are no minumum hints about the fact the server is properly configured (no "bind" directive is used in order to restrict the server to certain interfaces, nor a password is set), clients connecting from external intefaces are refused with an error explaining what to do in order to fix the issue. Clients connecting from the IPv4 and IPv6 lookback interfaces are still accepted normally, similarly Unix domain socket connections are not restricted in any way.
-
- 05 Oct, 2015 1 commit
-
-
antirez authored
-
- 28 Jul, 2015 1 commit
-
-
antirez authored
-
- 27 Jul, 2015 2 commits
- 26 Jul, 2015 6 commits
- 16 Jul, 2015 1 commit
-
-
Jiahao Huang authored
-
- 12 Mar, 2015 2 commits
- 11 Mar, 2015 3 commits
- 10 Mar, 2015 2 commits
-
-
antirez authored
-
antirez authored
Not perfect since The Solution IMHO is to have a DSL with a table of configuration functions with type, limits, and aux functions to handle the odd ones. However this hacky macro solution is already better and forces to put limits in the range of numerical fields. More field types to be refactored in the next commits hopefully.
-
- 08 Mar, 2015 1 commit
-
-
antirez authored
-
- 12 Feb, 2015 1 commit
-
-
antirez authored
Related to PR #2357.
-
- 04 Feb, 2015 1 commit
-
-
Chris Lamb authored
Signed-off-by:
Chris Lamb <chris@chris-lamb.co.uk>
-