hi Kamal, > If we add the timeout in the ListOffsetsRequest.json, then when old clients talk with the new broker, we don't have a timeout to set on the server. Moved adding the timeout to the
Personally, adding the timeout to ListOffsetsRequest open a room to clients to pick up the "suitable" wait time. The other purgatory-related requests (fetch, produce, heartbeat, delete_record) having similar config in request-level. Maybe we can keep both request-level timeout and server-side config. If the request does not define the timeout (from old client), we use server-side config instead. WDYT? Best, Chia-PIng
