You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When partitions are reassigned to different brokers there's a time window where the old leader is no longer a replica of the partition but the client has not yet updated its metadata to find the new leader. In these circumstances the client should refresh its metadata to obtain the new leader.
This applies to:
ProduceRequest (mark leader as unavailable, refresh metadata, and schedule retry)
FetchRequest (mark leader as unavailable, refresh metadata, and back off next fetch)
ListOffsets (refresh metadata, retry)
We'll handle ERR_KAFKA_STORAGE_ERROR the same way.
The text was updated successfully, but these errors were encountered:
When partitions are reassigned to different brokers there's a time window where the old leader is no longer a replica of the partition but the client has not yet updated its metadata to find the new leader. In these circumstances the client should refresh its metadata to obtain the new leader.
This applies to:
We'll handle ERR_KAFKA_STORAGE_ERROR the same way.
The text was updated successfully, but these errors were encountered: