The proposed change is backward compatible.
- Use connections.max.idle.ms to instead of connect.timeout.ms
- : it will close idle connections after the number of milliseconds specified by this config, default is 9 minutes
But this parameter is only work for the connection phase, if the channel is connecting, this parameter can not close the channel.
- Enhanced request.timeout.ms to support the connecting timeout: we are using request.timeout.ms to control not only for the request(produce request or fetch request), but also for the connecting phase.
If we only use the request.timeout for the connect and process request, it is not flexible for some case： for example we need the connecting phase to a short time(5s), and the request for a longer time(40s).