Description
NotLeaderForPartitionException is logged at the ERROR level with a full stack trace. But really this is just an informational message on the server when a client with stale metadata sends requests to the wrong leader for a partition. This floods the logs either if there are many clients or few clients sending many topics (migration tool or mirror maker). This should probably be logged at WARN and without the stack trace
Attachments
Attachments
Issue Links
- is blocked by
-
KAFKA-877 Still getting kafka.common.NotLeaderForPartitionException
- Resolved