Module admin 

The admin client: enough to create a topic, inspect a cluster, and trim a log — no more.

Two routing rules, and both are load-bearing:

• Topic creation, deletion and expansion go to the controller. Every other broker answers NOT_CONTROLLER (41), and the controller moves on election, so a 41 forgets the cached controller and asks again rather than retrying the same broker forever. This is the same shape as the producer’s NOT_COORDINATOR handling, for the same reason.
• DeleteRecords goes to the partition leader, like a produce or a fetch. It is not a cluster operation; it moves one log’s start offset.

librdkafka’s admin surface is far larger. This is the subset that makes it possible to write a test suite and an operational tool without reaching for a second client, which is the whole reason it exists.

Structs

Admin

Administrative operations, on one core like everything else here.

BrokerInfo

One broker, as the cluster describes itself.

NewTopic

A topic to create.