Database Reference
In-Depth Information
# Hostname the broker will bind to and
# advertise to producers and consumers.
# If not set, the server will bind to all
# interfaces and advertise the value returned from
# from java.net.InetAddress.getCanonicalHostName().
#host.name=localhost
These next two options control the number of threads that Kafka uses for
processing network requests and managing the log files. In older versions
of Kafka, there was only a single option to set the number of threads
kafka.num .threads
. The new setting allows for greater flexibility in
tuning the Kafka cluster. The default value for
num.network.threads
is 3 and for
num.io.threads
it is 8. The recommendation for
num.network.threads
of 3 threads is probably sufficient for most use
cases. For
num.io.threads
, the recommendation is that the number of
threads equal the number of disks used for log storage.
# The number of threads handling network requests
num.network.threads=3
# The number of threads doing disk I/O
num.io.threads=8
# The number of requests that can be queued for I/O
before network
# threads stop reading
#queued.max.requests=
The next settings control the size of the socket buffers and requests. For
multi-datacenter transfers, the LinkedIn reference configuration increases
these values to 2MB from the following 1MB configuration. If these settings
arecommentedout,thedefaultisarelativelysmall100KBbuffersize,which
may be too small for a high-volume production environment. It is usually
not necessary to modify the maximum request size, which is set to 100MB
in this case:
# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=1048576
# The receive buffer (SO_RCVBUF) used by the socket
server
socket.receive.buffer.bytes=1048576
