maximum number of bytes to include in the message set
maximum time to wait (msecs) for messages
minimum number of bytes to accumulate on the server before returning messages
number of consumer queue buffers, each one has size of consumerMaxBytes, must be at least 2
size of the deserializer buffer
maximum time to wait (msecs) when bundling fetch requests the longer the waiting, the more fetch requests may be accumulated the fetcher may bundle faster if there are more requests than fetcherBundleMinRequests
minimum number of fetch requests to accumulate before bundling them into one request the fetcher may bundle less requests if the fetcherBundleMaxWaitTime elapses first
number of retries to perform when waiting for leader election, 0 = retry infinitely
time to wait (msecs) between retries when waiting for leader election
number of retries to perform when refreshing the metadata, 0 = retry infinitely
time to wait (msecs) between retries when refreshing the metadata
maximum time (msecs) the broker should wait for the receipt of the number of acknowledgements (producerRequiredAcks)
maximum time to wait (msecs) for a message set. Batches of messages are prepared up to maximum buffer size or up to batch timeout, whichever happens first
default compression mode for the producers, may be overriden in the Producer constructor
valid only for GZIP compression, compression level between 1 and 9: 1 gives best speed, 9 gives best compression
maximum number of bytes to include in the message set, this must not be larger than consumerMaxBytes, otherwise, the consumers may not handle the message sets.
number of producer queue buffers, each one has size of producerMaxBytes, must be at least 2
this field indicates how many acknowledgements the servers should receive before responding to the request if it is 0 the server will not send any response (this is the only case where the server will not reply to a request) if it is 1, the server will wait the data is written to the local log before sending a response if it is -1 the server will block until the message is committed by all in sync replicas before sending a response for any number > 1 the server will block waiting for this number of acknowledgements to occur (but the server will never wait for more acknowledgements than there are in-sync replicas)
maximum time to wait (msecs) when bundling produce requests the longer the waiting, the more produce requests may be accumulated the pusher may bundle faster if there are more requests than pusherBundleMinRequests
minimum number of producer requests to accumulate before bundling them into one request the pusher may bundle less requests if the pusherBundleMaxWaitTime elapses first
size of the serializer buffer