...
public static final String NETWORK_REQUEST_TIMEOUT_CONFIG = "network.request.timeout.ms";
private static final String NETWORK_REQUEST_TIMEOUT_DOC = "The configuration controls the maximum amount of time the producer will wait for the response of a request. If the "
...
There is an existing configuration TIMEOUT_CONFIG, which is really a server side timeout specifying the maximum amount of time brokers can wait before send back the response. In order to avoid future confusion, for KafkaProducer, we might also want to change TIMEOUT_CONFIG to REPLICATION_TIMEOUT_CONFIG.
End state of timeouts in producer
- max.send.block.ms - This timeout defines how long the producer.send() method can block (we will enforce this for both metadata and blocking on buffer full in a separate ticket)
- linger.ms - The maximum time the producer will buffer the records for batch before sending it out.
- batch.timeout.ms - In some cases, the leader broker information of a batch could be unavailable after the batch is ready to be sent (i.e. batch is full or reached linger.ms). This configuration define the maximum time the producer will wait for the necessary broker information before it fail the batches.
- network.request.timeout.ms - This timeout is used when producer sends request to brokers through TCP connections. It specifies how long the producer should wait for the response.
- replication.timeout.ms - This is a server side configuration. It defines how long a server will wait for the records to be replicated to followers.
Proposed Changes
Because the NetworkClient works in an async way. We need to keep track of the send time for each request. So the implementation will the following:
...