Skip to content

Inspect delivery on a cluster

Read the consumer groups behind the workers' subscriptions on a cluster. How they are laid out is in Pub/Sub Delivery and Scaling.

Against the Redis primary (namespace redis in the reference deployment):

# one group per API pod per topic, with its last-delivered id and pending count
redis-cli XINFO GROUPS <topic>

# anything a closed subscription's parked reader left behind
redis-cli XPENDING <topic> <api-pod-name>

The worker lifecycle event stream (sys.workmanager.worker.lifecycle) carries worker_id and topic, which is the quickest way to see which workers a topic reaches. Shard membership is in ListWorkers (shard, shard_size, shard_index).