title: kafka + This server is not the leader for that topic-partition + kafka producer
body: <p>We are get many errors from <code>server.log</code> from each of <code>3</code> kafka machines ( we have <code>3</code> kafka in the cluster )</p>
  
  <pre><code>[2019-12-05 13:25:09,529] ERROR [ReplicaFetcherThread-0-1], Error for partition [jdty.dee.rules.time,91] to broker 1001:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
  [2019-12-05 13:25:09,529] ERROR [ReplicaFetcherThread-0-1], Error for partition [jdty.dee.export.profiles,96] to broker 1001:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
  [2019-12-05 13:25:09,529] ERROR [ReplicaFetcherThread-0-1], Error for partition [jdty.dee.control.tt.state,40] to broker 1001:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
  [2019-12-05 13:25:09,529] ERROR [ReplicaFetcherThread-0-1], Error for partition [jdty.dee.control.tt,67] to broker 1001:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
  </code></pre>
  
  <p>from my understanding each topic is served by one or multiple Brokers - one is leader and the remaining brokers are followers.</p>
  
  <p>A producer needs to send new messages to the leader Broker which internally replicate the data to all followers.</p>
  
  <p>I assume, that your producer client does not connect to the correct Broker, its connect to a follower instead of the leader, and this follower rejects your send request.</p>
  
  <p>so my question is - how to configure the producer configuration in order to avoid such these errors?</p>