When we attempt to route a fetch request for which we have no record of its topic we issue a warning since it is impossible to route correctly.
We were previously including the topic name (topic field) in the warning but the kafka protocol has deprecated the topic name in favor of the topic uuid (topic_id field) .
This was resulting in warnings that look like:
no known partition replica for topic "", routing message to a random node so that a NOT_LEADER_OR_FOLLOWER or similar error is returned to the client
So this PR now uses the topic name if provided and fallsback to the topic id when needed.
When we attempt to route a fetch request for which we have no record of its topic we issue a warning since it is impossible to route correctly. We were previously including the topic name (
topic
field) in the warning but the kafka protocol has deprecated the topic name in favor of the topic uuid (topic_id
field) . This was resulting in warnings that look like:no known partition replica for topic "", routing message to a random node so that a NOT_LEADER_OR_FOLLOWER or similar error is returned to the client
So this PR now uses the topic name if provided and fallsback to the topic id when needed.