Files
kumomta/docs/reference/kcli/inspect-ready-q.md
Wez Furlong 407379dd36 track sched->readyq fan in, clean up some internals
This commit removes the queue_name_for_config_change_purposes_only wart
from inside the readyq machinery.  This field had a bunch of caveats
and could in some cases become stale if the originating scheduled
queue had aged out.

It's been replaced by a HashSet of Weak refs back to the associated
scheduled queues so that it is now possible to walk the reverse of
the fan-in graph when we need to.
2026-06-25 13:41:01 +01:00

32 lines
1.0 KiB
Markdown

---
tags:
- ops
- debugging
---
# kcli inspect-ready-q
Returns information about a ready queue: its egress identity, effective state (throttles, suspensions, ready and connection counts), and, optionally, the dispatcher tasks that are currently handling its connections plus the egress path configuration in effect
**Usage:** `kcli inspect-ready-q [OPTIONS] <QUEUE_NAME>`
## Arguments
* `<QUEUE_NAME>` — The name of the ready queue to inspect
## Options
* `--connections` — Show the per-connection dispatcher state (phase, time in phase, message counters, etc.). Off by default since a busy queue can have many dispatchers
* `--config` — Include the egress path configuration snapshot. Off by default because the config can be large
* `--sched-q` — Include the list of scheduled queues that currently feed this ready queue. Off by default; can be expensive on ready queues with high fan-in
* `--json` — Output the response as pretty-printed JSON. Mutually exclusive with the other flags; the JSON output always carries the full payload