You are browsing a read-only backup copy of Wikitech. The primary site can be found at wikitech.wikimedia.org
Redis is used in Wikimedia production for:
- changeprop (role::redis::misc)
- stashing user sessions ($wgSessionCacheType) and the data stored in the main stash ($wgMainStash).
- As a cache and queue backend in ORES
- Receiver of sampled profile data from Xenon, as part as the sampling/profiling pipeline.
Role redis::misc (Redis 3.x)
redis::misc is for our general purpose master-slave cluster in eqiad and codfw DCs. Each
rdb* node has 5 instances (ports 6378, 6379, 6380, 6381, 6382) because redis is sigle threaded.
Each master has its respected slave. Masters use odd numbers (e.g. rdb1005) and slaves an even one (e.g. rdb1006). Master-slave instances use the same ports e.g.
rdb1005:6379 is the master of
- rdb1005 (m) - rdb1005 (s)
- rdb1009 (m) - rdb1010 (s)
- rdb2003 (m) - rdb2004 (s)
- rdb2005 (m) - rdb2006 (s)
Change propagation (or changeprop) is a service running on
scb* servers listening to topics on Kafka for events, and translates them into http requests to various systems. It is also responsible for cache evictions to happen on all services like RESTBase. Changeprop talks to redis via Nutcracker.
- Kibana changeprop Dashboard
Related puppet code
- Instance passwords can be easily found under
- Grafana redis::misc Dashboard
You can use the
redis-cli utility to make queries against Redis. In order to make queries against Redis, you need to be on a production server
such as tin that can access the servers and has
redis-cli installed, and give the command.
This information is outdated.
- redis-cli -a password-here -h rdb1001
(Grab the password out of /srv/mediawiki/private/PrivateSettings.php on tin, the server where it runs, look for
$wmgRedisPassword in it.)
This will leave you at a redis prompt where you can enter commands interactively.
Some useful commands
info will give you a pile of status information about the server, including the number of keys near the end of the output.
keys pattern-here will give you a list of all keys matching the given pattern. Use this sparingly, there's a lot of keys in there and the query will take (at least) several seconds to complete.
quit closes the connection.
Commands are easy, they all depend on the data type (hash, set, list, etc). Here's a quick reference.
Configuration is likewise pretty straightforward with perhaps the exception of the snapshotting, aof and memory settings; here's the sample config file.