summaryrefslogtreecommitdiff
path: root/redis.conf
Commit message (Collapse)AuthorAgeFilesLines
* Cluster: ability to prevent slaves from failing over their masters.antirez2018-03-141-0/+10
| | | | | | | | | | | | | | | | | | | | | | This commit, in some parts derived from PR #3041 which is no longer possible to merge (because the user deleted the original branch), implements the ability of slaves to have a special configuration preventing that they try to start a failover when the master is failing. There are multiple reasons for wanting this, and the feautre was requested in issue #3021 time ago. The differences between this patch and the original PR are the following: 1. The flag is saved/loaded on the nodes configuration. 2. The 'myself' node is now flag-aware, the flag is updated as needed when the configuration is changed via CONFIG SET. 3. The flag name uses NOFAILOVER instead of NO_FAILOVER to be consistent with existing NOADDR. 4. The redis.conf documentation was rewritten. Thanks to @deep011 for the original patch.
* Document new protocol options in #4568 into redis.conf.antirez2018-01-111-0/+14
|
* fix some notesWuYunlong2017-12-051-1/+3
|
* Merge pull request #4165 from zyegfryed/patch-1Salvatore Sanfilippo2017-11-281-3/+3
|\ | | | | Fix some typos
| * Fix some typosSébastien Fievet2017-07-261-3/+3
| |
* | Typo fixShaun Webb2017-07-271-1/+1
|/
* Defrag: document the feature in redis.conf.antirez2017-01-111-6/+49
|
* active memory defragmentationoranagra2016-12-301-0/+20
|
* Merge pull request #3498 from ZhukovAlexander/patch-1Salvatore Sanfilippo2016-12-201-1/+1
|\ | | | | Fix an article usage
| * Fix an article usageAlexander Zhukov2016-09-121-1/+1
| |
* | Only show Redis logo if logging to stdout / TTY.antirez2016-12-191-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | You can still force the logo in the normal logs. For motivations, check issue #3112. For me the reason is that actually the logo is nice to have in interactive sessions, but inside the logs kinda loses its usefulness, but for the ability of users to recognize restarts easily: for this reason the new startup sequence shows a one liner ASCII "wave" so that there is still a bit of visual clue. Startup logging was modified in order to log events in more obvious ways, and to log more events. Also certain important informations are now more easy to parse/grep since they are printed in field=value style. The option --always-show-logo in redis.conf was added, defaulting to no.
* | Merge branch 'psync2' into unstableantirez2016-11-171-0/+4
|\ \
| * | PSYNC2: different improvements to Redis replication.antirez2016-11-091-0/+4
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The gist of the changes is that now, partial resynchronizations between slaves and masters (without the need of a full resync with RDB transfer and so forth), work in a number of cases when it was impossible in the past. For instance: 1. When a slave is promoted to mastrer, the slaves of the old master can partially resynchronize with the new master. 2. Chained slalves (slaves of slaves) can be moved to replicate to other slaves or the master itsef, without requiring a full resync. 3. The master itself, after being turned into a slave, is able to partially resynchronize with the new master, when it joins replication again. In order to obtain this, the following main changes were operated: * Slaves also take a replication backlog, not just masters. * Same stream replication for all the slaves and sub slaves. The replication stream is identical from the top level master to its slaves and is also the same from the slaves to their sub-slaves and so forth. This means that if a slave is later promoted to master, it has the same replication backlong, and can partially resynchronize with its slaves (that were previously slaves of the old master). * A given replication history is no longer identified by the `runid` of a Redis node. There is instead a `replication ID` which changes every time the instance has a new history no longer coherent with the past one. So, for example, slaves publish the same replication history of their master, however when they are turned into masters, they publish a new replication ID, but still remember the old ID, so that they are able to partially resynchronize with slaves of the old master (up to a given offset). * The replication protocol was slightly modified so that a new extended +CONTINUE reply from the master is able to inform the slave of a replication ID change. * REPLCONF CAPA is used in order to notify masters that a slave is able to understand the new +CONTINUE reply. * The RDB file was extended with an auxiliary field that is able to select a given DB after loading in the slave, so that the slave can continue receiving the replication stream from the point it was disconnected without requiring the master to insert "SELECT" statements. This is useful in order to guarantee the "same stream" property, because the slave must be able to accumulate an identical backlog. * Slave pings to sub-slaves are now sent in a special form, when the top-level master is disconnected, in order to don't interfer with the replication stream. We just use out of band "\n" bytes as in other parts of the Redis protocol. An old design document is available here: https://gist.github.com/antirez/ae068f95c0d084891305 However the implementation is not identical to the description because during the work to implement it, different changes were needed in order to make things working well.
* | TypoMichel Tresseras2016-10-241-1/+1
|/
* Document RDB preamble in AOF rewrites in redis.conf.antirez2016-08-241-0/+14
|
* Ability of slave to announce arbitrary ip/port to master.antirez2016-07-271-0/+29
| | | | | | | | | 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.
* LFU: make counter log factor and decay time configurable.lfuantirez2016-07-201-11/+71
|
* Enable tcp-keepalive by default.antirez2016-06-131-2/+3
|
* Merge pull request #3180 from bogdanvlviv/fix_pidfileSalvatore Sanfilippo2016-06-101-1/+1
|\ | | | | fix pidfile in redis.conf
| * fix pidfile in redis.confbogdanvlviv2016-04-191-1/+1
| |
* | Modules: first preview 31 March 2016.antirez2016-05-101-0/+8
|/
* Cluster announce ip/port/bus-port documented in redis.conf.antirez2016-02-011-0/+33
|
* New security feature: Redis protected mode.antirez2016-01-071-0/+19
| | | | | | | | | | | | | | | | | | | | | 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.
* Fix typo UNCOMMENT -> COMMENT in example redis.conf.antirez2015-12-031-1/+1
|
* Redis.conf example: make clear user must pass its path as argument.antirez2015-10-151-1/+6
|
* Lazyfree options documented in the example redis.conf.lazyfreeantirez2015-10-051-1/+52
|
* Merge branch 'unstable' of github.com:/antirez/redis into unstableantirez2015-04-271-1/+1
|\
| * Added reference to IANA ticket for port 6379Itamar Haber2015-04-241-1/+1
| | | | | | Just so it's extra official :smile:
* | Example redis.conf doc about pidfile fixed.antirez2015-04-261-2/+9
|/ | | | An user changed the behavior via a PR without upgrading the doc.
* 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.
* Unify to uppercase the headlineMasahiko Sawada2015-02-121-1/+1
|
* Supervise redis processes only if configuredMatt Stancliff2015-01-091-0/+11
| | | | | | | | | | | Adds configuration option 'supervised [no | upstart | systemd | auto]' Also removed 'bzero' from the previous implementation because it's 2015. (We could actually statically initialize those structs, but clang throws an invalid warning when we try, so it looks bad even though it isn't bad.) Fixes #2264
* Advertise Redis Cluster as experimental in redis.conf.antirez2015-01-081-0/+6
|
* Config: Add quicklist, remove old list optionsMatt Stancliff2015-01-021-5/+30
| | | | | | | | | | | | | This removes: - list-max-ziplist-entries - list-max-ziplist-value This adds: - list-max-ziplist-size - list-compress-depth Also updates config file with new sections and updates tests to use quicklist settings instead of old list settings.
* Merge pull request #2117 from mariano-perez-rodriguez/patch-4Salvatore Sanfilippo2014-12-111-2/+2
|\ | | | | Typo fixes in redis.conf
| * Typo fixes in redis.confMariano Pérez Rodríguez2014-10-311-2/+2
| | | | | | | | | | | | Fix two typos in redis.conf: - "trnasfers" --> "transfers" - "enalbed" --> "enabled"
* | Mark diskless replication as experimental in redis.conf.antirez2014-12-021-0/+4
|/
* Document repl-diskless-sync-delay in redis.conf.antirez2014-10-271-0/+12
|
* Diskless replication documented inside example redis.conf.antirez2014-10-241-0/+27
|
* redis.conf small grammar fixMiguel Parramon2014-09-291-1/+1
| | | | | | :smile: Closes #2034
* Clean up text throughout projectMatt Stancliff2014-09-291-12/+12
| | | | | | | | | | - Remove trailing newlines from redis.conf - Fix comment misspelling - Clarifies zipEncodeLength usage and a C API mention (#1243, #1242) - Fix cluster typos (inspired by @papanikge #1507) - Fix rewite -> rewrite in a few places (inspired by #682) Closes #1243, #1242, #1507
* Grammar and typo fixes in redis.confBen2014-09-291-17/+16
| | | | Closes #1441
* Fix typo in redis.confJan-Erik Rediger2014-09-291-1/+1
| | | | Closes #1713
* Improve disable save comment in redis.confManuel Meurer2014-09-291-1/+1
| | | | Closes #1897
* Cluster: new option to work with partial slots coverage.antirez2014-09-171-0/+13
|
* Make aof-load-truncated option actually configurable.antirez2014-09-081-0/+24
|
* Change unixsocketperm comment to 700 from 755Edgars Irmejs2014-08-071-1/+1
| | | | | | | | According to unix manuals, "Connecting to the socket object requires read/write permission." -- mode 755 is useless for anybody other than the owner. Fixes #1696
* * fixed doc URL for keyspace eventsvps2014-07-281-1/+1
|
* Example redis.conf: improve slaveof description.antirez2014-07-251-3/+12
|
View Lorry Controller Status