failed due to leader not local for partition usually occurs in response
to client requests that make a fetch or produce request to a partition, to
the wrong broker (e.g. to a follower and not the leader for the
partition). Clients need to make a meta-data request first to determine
the leader
Hello,
For some reason, I'm getting this failed due to Leader not local for
partition on my brokers. I can't send the logs, but I'm going to try to
describe what I see. First, note that this is a fresh set of brokers with no
data.
I do see a series of messages stating Expanding ISR for
