Tag
tools
Redis and Valkey ACL rules are short and easy to get wrong. +@all -flushall and -flushall +@all look alike and grant different things. %R~config:* reads but doesn’t …
tools
A Redis server reads its config file once, when it starts, and stops at the first line it can’t use. It prints that line and exits. Fix it, restart, and it stops at …
tools
How much memory do fifty million sessions need? The usual answer is a test: load a sample, read INFO memory, multiply. That works for the version you tested, with the key …
tools
Code that ran fine against a single Redis or Valkey server often breaks the day it moves to a cluster. An MGET, a MULTI block or a Lua script that touched three keys now …
tools
A key-value store has no tables and no schema to read. Everything sits in one flat list of keys, and the only structure is whatever people built into the names. After a …
tools
The slow way to load a million keys into Redis or Valkey is a loop that sends a command, waits for the answer, and sends the next. Most of the time goes on the waiting. …
tools
A Redis server is using 40 GB and nobody is sure what’s in it. The usual tools all ask the server itself. --bigkeys scans every key, MEMORY USAGE asks about one key …
tools
A Redis server is running hot and the question is what with. INFO commandstats counts commands but can’t say which keys or which clients. The slow log only keeps …
tools
Someone runs GET session:42 on a production Redis server to see why a user is stuck, and gets back …