KIP-1243 — Consistent Metadata Reads

Discussion KRaftProtocol

Introduces consistent metadata reads by allowing clients to request metadata responses that reflect at least a specified metadata offset, ensuring they do not observe stale cached state that lags committed cluster metadata. Currently, least-loaded broker routing returns metadata from the broker's in-memory cache, which may be behind the committed cluster metadata partition offset, causing clients to see stale topic or partition state immediately after administrative changes.

Details