Operations
Operate WuKongIM clusters through verifiable, stoppable, and reversible procedures.
Operations is not about merely completing an action. Each step should leave safety evidence. Observe the cluster, freeze the change, execute one bounded step, and verify both product and cluster state. Stop when the evidence is incomplete.
Every deployment is a cluster
A one-node deployment is still a single-node cluster. Scaling, backup, restore, and upgrades cannot bypass Controller, Slot, or Channel semantics. The physical hash-slot count remains 256.
Standard change loop
- Observe: establish baselines for
/readyz, nodes, Controller, Slots, Channels, queues, disk, and product errors. - Plan: record artifact, configuration, objective, permissions, stop conditions, rollback, and owner.
- Change: advance one bounded step at a time; do not overlap topology operations that affect one another.
- Verify: wait for readiness and verify message send, receive, reconnect, backlog, and storage signals.
- Retain evidence: save audit records, task results, metric snapshots, and the resulting node inventory.
Choose a task
Manager
Understand access boundaries, permissions, views, and high-risk writes.
Health & Monitoring
Separate liveness, readiness, metrics, Top, and diagnostics.
Scaling
Join explicitly, allocate resources, and drain a node safely.
Backup & Restore
Save, test, and verify backups, then restore under maintenance.
Upgrade & Migration
Confirm compatibility before choosing rolling or maintenance rollout.
Troubleshooting
Start from a symptom and collect trustworthy evidence by cost.
Before starting
- Use a controlled Manager network and a least-privilege account.
- Complete the Production Checklist.
- Require a storage test for the current plan revision and at least one complete, verified archive.
- Preserve resource headroom for large groups, high message rates, many channels, and many online users.
- Treat unknown, stale, or conflicting state as a stop condition, not a reason to proceed.
When you need to choose a command-line or diagnostic surface, continue to Tools. Tool output is evidence; it never replaces approval or a safety gate.