Kafka Error MISMATCHED_ENDPOINT_TYPE
Error code 114 · Non-retriable KRaft
The request was sent to an endpoint of the wrong type.
Common Causes
- A KRaft-specific request (e.g., a controller API call) was sent to a broker endpoint instead of the controller endpoint, or vice versa — typically a client or tool misconfiguration pointing at the wrong listener.
- In a combined KRaft mode deployment (broker+controller roles on the same node), a request intended for the controller role was routed to the broker listener (or vice versa) due to incorrect listener configuration.
- Admin tooling or custom code using hard-coded ports hit the wrong listener type (e.g., targeting port 9092 broker listener for a controller-only API).
Solutions
- Verify the `--bootstrap-server` or `--bootstrap-controller` flag used with Kafka CLI tools: controller APIs require the controller listener endpoint (typically port 9093 or as defined in `controller.listener.names`), not the broker listener.
- Check broker config `listeners` and `controller.listener.names` to confirm endpoint separation. In production, keep broker and controller listeners on distinct ports to avoid routing confusion.
- For admin clients, use `AdminClient` with the broker bootstrap server for data-plane admin operations; controller-plane operations (metadata quorum, etc.) require the controller endpoint.
Diagnostic Commands
# Check KRaft metadata quorum status
kafka-metadata-quorum.sh --bootstrap-controller <controller-host>:9093 --command-config admin.properties describe --status
# Look for endpoint errors in logs
grep 'MISMATCHED_ENDPOINT\|endpoint type\|listener' /var/log/kafka/server.log | tail -50
Debugging Kafka errors? Conduktor Console gives you real-time visibility into your cluster. Explore all errors in the Error Decoder.