| <ul class="config-list"> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="key.serializer"></a> |
| <a href="#key.serializer">key.serializer</a> |
| </h4> |
| <p>Serializer class for key that implements the <code>org.apache.kafka.common.serialization.Serializer</code> interface.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>class</td></tr> |
| <tr><th>Default:</th><td></td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="value.serializer"></a> |
| <a href="#value.serializer">value.serializer</a> |
| </h4> |
| <p>Serializer class for value that implements the <code>org.apache.kafka.common.serialization.Serializer</code> interface.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>class</td></tr> |
| <tr><th>Default:</th><td></td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"><a id="acks" class="anchor-link"></a><a href="#acks">acks</a></h4> |
| <p>The number of acknowledgments the producer requires the leader to have received before considering a request complete. This controls the durability of records that are sent. The following settings are allowed: <ul> <li><code>acks=0</code> If set to zero then the producer will not wait for any acknowledgment from the server at all. The record will be immediately added to the socket buffer and considered sent. No guarantee can be made that the server has received the record in this case, and the <code>retries</code> configuration will not take effect (as the client won't generally know of any failures). The offset given back for each record will always be set to <code>-1</code>. <li><code>acks=1</code> This will mean the leader will write the record to its local log but will respond without awaiting full acknowledgement from all followers. In this case should the leader fail immediately after acknowledging the record but before the followers have replicated it then the record will be lost. <li><code>acks=all</code> This means the leader will wait for the full set of in-sync replicas to acknowledge the record. This guarantees that the record will not be lost as long as at least one in-sync replica remains alive. This is the strongest available guarantee. This is equivalent to the acks=-1 setting.</ul></p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>1</td></tr> |
| <tr><th>Valid Values:</th><td>[all, -1, 0, 1]</td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="bootstrap.servers"></a> |
| <a href="#bootstrap.servers">bootstrap.servers</a> |
| </h4> |
| <p>A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. The client will make use of all servers irrespective of which servers are specified here for bootstrapping—this list only impacts the initial hosts used to discover the full set of servers. This list should be in the form <code>host1:port1,host2:port2,...</code>. Since these servers are just used for the initial connection to discover the full cluster membership (which may change dynamically), this list need not contain the full set of servers (you may want more than one, though, in case a server is down).</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>list</td></tr> |
| <tr><th>Default:</th><td>""</td></tr> |
| <tr><th>Valid Values:</th><td>non-null string</td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="buffer.memory"></a> |
| <a href="#buffer.memory">buffer.memory</a> |
| </h4> |
| <p>The total bytes of memory the producer can use to buffer records waiting to be sent to the server. If records are sent faster than they can be delivered to the server the producer will block for <code>max.block.ms</code> after which it will throw an exception.<p>This setting should correspond roughly to the total memory the producer will use, but is not a hard bound since not all memory the producer uses is used for buffering. Some additional memory will be used for compression (if compression is enabled) as well as for maintaining in-flight requests.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>33554432</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="compression.type"></a> |
| <a href="#compression.type">compression.type</a> |
| </h4> |
| <p>The compression type for all data generated by the producer. The default is none (i.e. no compression). Valid values are <code>none</code>, <code>gzip</code>, <code>snappy</code>, <code>lz4</code>, or <code>zstd</code>. Compression is of full batches of data, so the efficacy of batching will also impact the compression ratio (more batching means better compression).</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>none</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"><a id="retries" class="anchor-link"></a><a href="#retries">retries</a></h4> |
| <p>Setting a value greater than zero will cause the client to resend any record whose send fails with a potentially transient error. Note that this retry is no different than if the client resent the record upon receiving the error. Allowing retries without setting <code>max.in.flight.requests.per.connection</code> to 1 will potentially change the ordering of records because if two batches are sent to a single partition, and the first fails and is retried but the second succeeds, then the records in the second batch may appear first. Note additionally that produce requests will be failed before the number of retries has been exhausted if the timeout configured by <code>delivery.timeout.ms</code> expires first before successful acknowledgement. Users should generally prefer to leave this config unset and instead use <code>delivery.timeout.ms</code> to control retry behavior.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>2147483647</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...,2147483647]</td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.key.password"></a> |
| <a href="#ssl.key.password">ssl.key.password</a> |
| </h4> |
| <p>The password of the private key in the key store file. This is optional for client.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>password</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.keystore.location"></a> |
| <a href="#ssl.keystore.location">ssl.keystore.location</a> |
| </h4> |
| <p>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.keystore.password"></a> |
| <a href="#ssl.keystore.password">ssl.keystore.password</a> |
| </h4> |
| <p>The store password for the key store file. This is optional for client and only needed if ssl.keystore.location is configured. </p> |
| <table><tbody> |
| <tr><th>Type:</th><td>password</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.truststore.location"></a> |
| <a href="#ssl.truststore.location">ssl.truststore.location</a> |
| </h4> |
| <p>The location of the trust store file. </p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.truststore.password"></a> |
| <a href="#ssl.truststore.password">ssl.truststore.password</a> |
| </h4> |
| <p>The password for the trust store file. If a password is not set access to the truststore is still available, but integrity checking is disabled.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>password</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>high</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="batch.size"></a> |
| <a href="#batch.size">batch.size</a> |
| </h4> |
| <p>The producer will attempt to batch records together into fewer requests whenever multiple records are being sent to the same partition. This helps performance on both the client and the server. This configuration controls the default batch size in bytes. <p>No attempt will be made to batch records larger than this size. <p>Requests sent to brokers will contain multiple batches, one for each partition with data available to be sent. <p>A small batch size will make batching less common and may reduce throughput (a batch size of zero will disable batching entirely). A very large batch size may use memory a bit more wastefully as we will always allocate a buffer of the specified batch size in anticipation of additional records.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>16384</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="client.dns.lookup"></a> |
| <a href="#client.dns.lookup">client.dns.lookup</a> |
| </h4> |
| <p>Controls how the client uses DNS lookups. If set to <code>use_all_dns_ips</code>, connect to each returned IP address in sequence until a successful connection is established. After a disconnection, the next IP is used. Once all IPs have been used once, the client resolves the IP(s) from the hostname again (both the JVM and the OS cache DNS name lookups, however). If set to <code>resolve_canonical_bootstrap_servers_only</code>, resolve each bootstrap address into a list of canonical names. After the bootstrap phase, this behaves the same as <code>use_all_dns_ips</code>. If set to <code>default</code> (deprecated), attempt to connect to the first IP address returned by the lookup, even if the lookup returns multiple IP addresses.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>use_all_dns_ips</td></tr> |
| <tr><th>Valid Values:</th><td>[default, use_all_dns_ips, resolve_canonical_bootstrap_servers_only]</td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="client.id"></a> |
| <a href="#client.id">client.id</a> |
| </h4> |
| <p>An id string to pass to the server when making requests. The purpose of this is to be able to track the source of requests beyond just ip/port by allowing a logical application name to be included in server-side request logging.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>""</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="connections.max.idle.ms"></a> |
| <a href="#connections.max.idle.ms">connections.max.idle.ms</a> |
| </h4> |
| <p>Close idle connections after the number of milliseconds specified by this config.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>540000 (9 minutes)</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="delivery.timeout.ms"></a> |
| <a href="#delivery.timeout.ms">delivery.timeout.ms</a> |
| </h4> |
| <p>An upper bound on the time to report success or failure after a call to <code>send()</code> returns. This limits the total time that a record will be delayed prior to sending, the time to await acknowledgement from the broker (if expected), and the time allowed for retriable send failures. The producer may report failure to send a record earlier than this config if either an unrecoverable error is encountered, the retries have been exhausted, or the record is added to a batch which reached an earlier delivery expiration deadline. The value of this config should be greater than or equal to the sum of <code>request.timeout.ms</code> and <code>linger.ms</code>.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>120000 (2 minutes)</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="linger.ms"></a> |
| <a href="#linger.ms">linger.ms</a> |
| </h4> |
| <p>The producer groups together any records that arrive in between request transmissions into a single batched request. Normally this occurs only under load when records arrive faster than they can be sent out. However in some circumstances the client may want to reduce the number of requests even under moderate load. This setting accomplishes this by adding a small amount of artificial delay—that is, rather than immediately sending out a record the producer will wait for up to the given delay to allow other records to be sent so that the sends can be batched together. This can be thought of as analogous to Nagle's algorithm in TCP. This setting gives the upper bound on the delay for batching: once we get <code>batch.size</code> worth of records for a partition it will be sent immediately regardless of this setting, however if we have fewer than this many bytes accumulated for this partition we will 'linger' for the specified time waiting for more records to show up. This setting defaults to 0 (i.e. no delay). Setting <code>linger.ms=5</code>, for example, would have the effect of reducing the number of requests sent but would add up to 5ms of latency to records sent in the absence of load.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>0</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="max.block.ms"></a> |
| <a href="#max.block.ms">max.block.ms</a> |
| </h4> |
| <p>The configuration controls how long <code>KafkaProducer.send()</code> and <code>KafkaProducer.partitionsFor()</code> will block.These methods can be blocked either because the buffer is full or metadata unavailable.Blocking in the user-supplied serializers or partitioner will not be counted against this timeout.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>60000 (1 minute)</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="max.request.size"></a> |
| <a href="#max.request.size">max.request.size</a> |
| </h4> |
| <p>The maximum size of a request in bytes. This setting will limit the number of record batches the producer will send in a single request to avoid sending huge requests. This is also effectively a cap on the maximum uncompressed record batch size. Note that the server has its own cap on the record batch size (after compression if compression is enabled) which may be different from this.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>1048576</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="partitioner.class"></a> |
| <a href="#partitioner.class">partitioner.class</a> |
| </h4> |
| <p>Partitioner class that implements the <code>org.apache.kafka.clients.producer.Partitioner</code> interface.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>class</td></tr> |
| <tr><th>Default:</th><td>org.apache.kafka.clients.producer.internals.DefaultPartitioner</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="receive.buffer.bytes"></a> |
| <a href="#receive.buffer.bytes">receive.buffer.bytes</a> |
| </h4> |
| <p>The size of the TCP receive buffer (SO_RCVBUF) to use when reading data. If the value is -1, the OS default will be used.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>32768 (32 kibibytes)</td></tr> |
| <tr><th>Valid Values:</th><td>[-1,...]</td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="request.timeout.ms"></a> |
| <a href="#request.timeout.ms">request.timeout.ms</a> |
| </h4> |
| <p>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted. This should be larger than <code>replica.lag.time.max.ms</code> (a broker configuration) to reduce the possibility of message duplication due to unnecessary producer retries.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>30000 (30 seconds)</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.client.callback.handler.class"></a> |
| <a href="#sasl.client.callback.handler.class">sasl.client.callback.handler.class</a> |
| </h4> |
| <p>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>class</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.jaas.config"></a> |
| <a href="#sasl.jaas.config">sasl.jaas.config</a> |
| </h4> |
| <p>JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described <a href="http://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">here</a>. The format for the value is: '<code>loginModuleClass controlFlag (optionName=optionValue)*;</code>'. For brokers, the config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.jaas.config=com.example.ScramLoginModule required;</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>password</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.kerberos.service.name"></a> |
| <a href="#sasl.kerberos.service.name">sasl.kerberos.service.name</a> |
| </h4> |
| <p>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.login.callback.handler.class"></a> |
| <a href="#sasl.login.callback.handler.class">sasl.login.callback.handler.class</a> |
| </h4> |
| <p>The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface. For brokers, login callback handler config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.callback.handler.class=com.example.CustomScramLoginCallbackHandler</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>class</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.login.class"></a> |
| <a href="#sasl.login.class">sasl.login.class</a> |
| </h4> |
| <p>The fully qualified name of a class that implements the Login interface. For brokers, login config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.class=com.example.CustomScramLogin</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>class</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.mechanism"></a> |
| <a href="#sasl.mechanism">sasl.mechanism</a> |
| </h4> |
| <p>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>GSSAPI</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="security.protocol"></a> |
| <a href="#security.protocol">security.protocol</a> |
| </h4> |
| <p>Protocol used to communicate with brokers. Valid values are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>PLAINTEXT</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="send.buffer.bytes"></a> |
| <a href="#send.buffer.bytes">send.buffer.bytes</a> |
| </h4> |
| <p>The size of the TCP send buffer (SO_SNDBUF) to use when sending data. If the value is -1, the OS default will be used.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>131072 (128 kibibytes)</td></tr> |
| <tr><th>Valid Values:</th><td>[-1,...]</td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.enabled.protocols"></a> |
| <a href="#ssl.enabled.protocols">ssl.enabled.protocols</a> |
| </h4> |
| <p>The list of protocols enabled for SSL connections. The default is 'TLSv1.2,TLSv1.3' when running with Java 11 or newer, 'TLSv1.2' otherwise. With the default value for Java 11, clients and servers will prefer TLSv1.3 if both support it and fallback to TLSv1.2 otherwise (assuming both support at least TLSv1.2). This default should be fine for most cases. Also see the config documentation for `ssl.protocol`.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>list</td></tr> |
| <tr><th>Default:</th><td>TLSv1.2</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.keystore.type"></a> |
| <a href="#ssl.keystore.type">ssl.keystore.type</a> |
| </h4> |
| <p>The file format of the key store file. This is optional for client.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>JKS</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.protocol"></a> |
| <a href="#ssl.protocol">ssl.protocol</a> |
| </h4> |
| <p>The SSL protocol used to generate the SSLContext. The default is 'TLSv1.3' when running with Java 11 or newer, 'TLSv1.2' otherwise. This value should be fine for most use cases. Allowed values in recent JVMs are 'TLSv1.2' and 'TLSv1.3'. 'TLS', 'TLSv1.1', 'SSL', 'SSLv2' and 'SSLv3' may be supported in older JVMs, but their usage is discouraged due to known security vulnerabilities. With the default value for this config and 'ssl.enabled.protocols', clients will downgrade to 'TLSv1.2' if the server does not support 'TLSv1.3'. If this config is set to 'TLSv1.2', clients will not use 'TLSv1.3' even if it is one of the values in ssl.enabled.protocols and the server only supports 'TLSv1.3'.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>TLSv1.2</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.provider"></a> |
| <a href="#ssl.provider">ssl.provider</a> |
| </h4> |
| <p>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.truststore.type"></a> |
| <a href="#ssl.truststore.type">ssl.truststore.type</a> |
| </h4> |
| <p>The file format of the trust store file.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>JKS</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>medium</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="enable.idempotence"></a> |
| <a href="#enable.idempotence">enable.idempotence</a> |
| </h4> |
| <p>When set to 'true', the producer will ensure that exactly one copy of each message is written in the stream. If 'false', producer retries due to broker failures, etc., may write duplicates of the retried message in the stream. Note that enabling idempotence requires <code>max.in.flight.requests.per.connection</code> to be less than or equal to 5, <code>retries</code> to be greater than 0 and <code>acks</code> must be 'all'. If these values are not explicitly set by the user, suitable values will be chosen. If incompatible values are set, a <code>ConfigException</code> will be thrown.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>boolean</td></tr> |
| <tr><th>Default:</th><td>false</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="interceptor.classes"></a> |
| <a href="#interceptor.classes">interceptor.classes</a> |
| </h4> |
| <p>A list of classes to use as interceptors. Implementing the <code>org.apache.kafka.clients.producer.ProducerInterceptor</code> interface allows you to intercept (and possibly mutate) the records received by the producer before they are published to the Kafka cluster. By default, there are no interceptors.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>list</td></tr> |
| <tr><th>Default:</th><td>""</td></tr> |
| <tr><th>Valid Values:</th><td>non-null string</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="max.in.flight.requests.per.connection"></a> |
| <a href="#max.in.flight.requests.per.connection">max.in.flight.requests.per.connection</a> |
| </h4> |
| <p>The maximum number of unacknowledged requests the client will send on a single connection before blocking. Note that if this setting is set to be greater than 1 and there are failed sends, there is a risk of message re-ordering due to retries (i.e., if retries are enabled).</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>5</td></tr> |
| <tr><th>Valid Values:</th><td>[1,...]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="metadata.max.age.ms"></a> |
| <a href="#metadata.max.age.ms">metadata.max.age.ms</a> |
| </h4> |
| <p>The period of time in milliseconds after which we force a refresh of metadata even if we haven't seen any partition leadership changes to proactively discover any new brokers or partitions.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>300000 (5 minutes)</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="metadata.max.idle.ms"></a> |
| <a href="#metadata.max.idle.ms">metadata.max.idle.ms</a> |
| </h4> |
| <p>Controls how long the producer will cache metadata for a topic that's idle. If the elapsed time since a topic was last produced to exceeds the metadata idle duration, then the topic's metadata is forgotten and the next access to it will force a metadata fetch request.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>300000 (5 minutes)</td></tr> |
| <tr><th>Valid Values:</th><td>[5000,...]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="metric.reporters"></a> |
| <a href="#metric.reporters">metric.reporters</a> |
| </h4> |
| <p>A list of classes to use as metrics reporters. Implementing the <code>org.apache.kafka.common.metrics.MetricsReporter</code> interface allows plugging in classes that will be notified of new metric creation. The JmxReporter is always included to register JMX statistics.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>list</td></tr> |
| <tr><th>Default:</th><td>""</td></tr> |
| <tr><th>Valid Values:</th><td>non-null string</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="metrics.num.samples"></a> |
| <a href="#metrics.num.samples">metrics.num.samples</a> |
| </h4> |
| <p>The number of samples maintained to compute metrics.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>2</td></tr> |
| <tr><th>Valid Values:</th><td>[1,...]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="metrics.recording.level"></a> |
| <a href="#metrics.recording.level">metrics.recording.level</a> |
| </h4> |
| <p>The highest recording level for metrics.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>INFO</td></tr> |
| <tr><th>Valid Values:</th><td>[INFO, DEBUG]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="metrics.sample.window.ms"></a> |
| <a href="#metrics.sample.window.ms">metrics.sample.window.ms</a> |
| </h4> |
| <p>The window of time a metrics sample is computed over.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>30000 (30 seconds)</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="reconnect.backoff.max.ms"></a> |
| <a href="#reconnect.backoff.max.ms">reconnect.backoff.max.ms</a> |
| </h4> |
| <p>The maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect. If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum. After calculating the backoff increase, 20% random jitter is added to avoid connection storms.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>1000 (1 second)</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="reconnect.backoff.ms"></a> |
| <a href="#reconnect.backoff.ms">reconnect.backoff.ms</a> |
| </h4> |
| <p>The base amount of time to wait before attempting to reconnect to a given host. This avoids repeatedly connecting to a host in a tight loop. This backoff applies to all connection attempts by the client to a broker.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>50</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="retry.backoff.ms"></a> |
| <a href="#retry.backoff.ms">retry.backoff.ms</a> |
| </h4> |
| <p>The amount of time to wait before attempting to retry a failed request to a given topic partition. This avoids repeatedly sending requests in a tight loop under some failure scenarios.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>100</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.kerberos.kinit.cmd"></a> |
| <a href="#sasl.kerberos.kinit.cmd">sasl.kerberos.kinit.cmd</a> |
| </h4> |
| <p>Kerberos kinit command path.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>/usr/bin/kinit</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.kerberos.min.time.before.relogin"></a> |
| <a href="#sasl.kerberos.min.time.before.relogin">sasl.kerberos.min.time.before.relogin</a> |
| </h4> |
| <p>Login thread sleep time between refresh attempts.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>long</td></tr> |
| <tr><th>Default:</th><td>60000</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.kerberos.ticket.renew.jitter"></a> |
| <a href="#sasl.kerberos.ticket.renew.jitter">sasl.kerberos.ticket.renew.jitter</a> |
| </h4> |
| <p>Percentage of random jitter added to the renewal time.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>double</td></tr> |
| <tr><th>Default:</th><td>0.05</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.kerberos.ticket.renew.window.factor"></a> |
| <a href="#sasl.kerberos.ticket.renew.window.factor">sasl.kerberos.ticket.renew.window.factor</a> |
| </h4> |
| <p>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>double</td></tr> |
| <tr><th>Default:</th><td>0.8</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.login.refresh.buffer.seconds"></a> |
| <a href="#sasl.login.refresh.buffer.seconds">sasl.login.refresh.buffer.seconds</a> |
| </h4> |
| <p>The amount of buffer time before credential expiration to maintain when refreshing a credential, in seconds. If a refresh would otherwise occur closer to expiration than the number of buffer seconds then the refresh will be moved up to maintain as much of the buffer time as possible. Legal values are between 0 and 3600 (1 hour); a default value of 300 (5 minutes) is used if no value is specified. This value and sasl.login.refresh.min.period.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>short</td></tr> |
| <tr><th>Default:</th><td>300</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...,3600]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.login.refresh.min.period.seconds"></a> |
| <a href="#sasl.login.refresh.min.period.seconds">sasl.login.refresh.min.period.seconds</a> |
| </h4> |
| <p>The desired minimum time for the login refresh thread to wait before refreshing a credential, in seconds. Legal values are between 0 and 900 (15 minutes); a default value of 60 (1 minute) is used if no value is specified. This value and sasl.login.refresh.buffer.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>short</td></tr> |
| <tr><th>Default:</th><td>60</td></tr> |
| <tr><th>Valid Values:</th><td>[0,...,900]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.login.refresh.window.factor"></a> |
| <a href="#sasl.login.refresh.window.factor">sasl.login.refresh.window.factor</a> |
| </h4> |
| <p>Login refresh thread will sleep until the specified window factor relative to the credential's lifetime has been reached, at which time it will try to refresh the credential. Legal values are between 0.5 (50%) and 1.0 (100%) inclusive; a default value of 0.8 (80%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>double</td></tr> |
| <tr><th>Default:</th><td>0.8</td></tr> |
| <tr><th>Valid Values:</th><td>[0.5,...,1.0]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="sasl.login.refresh.window.jitter"></a> |
| <a href="#sasl.login.refresh.window.jitter">sasl.login.refresh.window.jitter</a> |
| </h4> |
| <p>The maximum amount of random jitter relative to the credential's lifetime that is added to the login refresh thread's sleep time. Legal values are between 0 and 0.25 (25%) inclusive; a default value of 0.05 (5%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>double</td></tr> |
| <tr><th>Default:</th><td>0.05</td></tr> |
| <tr><th>Valid Values:</th><td>[0.0,...,0.25]</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="security.providers"></a> |
| <a href="#security.providers">security.providers</a> |
| </h4> |
| <p>A list of configurable creator classes each returning a provider implementing security algorithms. These classes should implement the <code>org.apache.kafka.common.security.auth.SecurityProviderCreator</code> interface.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.cipher.suites"></a> |
| <a href="#ssl.cipher.suites">ssl.cipher.suites</a> |
| </h4> |
| <p>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol. By default all the available cipher suites are supported.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>list</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.endpoint.identification.algorithm"></a> |
| <a href="#ssl.endpoint.identification.algorithm">ssl.endpoint.identification.algorithm</a> |
| </h4> |
| <p>The endpoint identification algorithm to validate server hostname using server certificate. </p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>https</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.engine.factory.class"></a> |
| <a href="#ssl.engine.factory.class">ssl.engine.factory.class</a> |
| </h4> |
| <p>The class of type org.apache.kafka.common.security.auth.SslEngineFactory to provide SSLEngine objects. Default value is org.apache.kafka.common.security.ssl.DefaultSslEngineFactory</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>class</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.keymanager.algorithm"></a> |
| <a href="#ssl.keymanager.algorithm">ssl.keymanager.algorithm</a> |
| </h4> |
| <p>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>SunX509</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.secure.random.implementation"></a> |
| <a href="#ssl.secure.random.implementation">ssl.secure.random.implementation</a> |
| </h4> |
| <p>The SecureRandom PRNG implementation to use for SSL cryptography operations. </p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="ssl.trustmanager.algorithm"></a> |
| <a href="#ssl.trustmanager.algorithm">ssl.trustmanager.algorithm</a> |
| </h4> |
| <p>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>PKIX</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="transaction.timeout.ms"></a> |
| <a href="#transaction.timeout.ms">transaction.timeout.ms</a> |
| </h4> |
| <p>The maximum amount of time in ms that the transaction coordinator will wait for a transaction status update from the producer before proactively aborting the ongoing transaction.If this value is larger than the transaction.max.timeout.ms setting in the broker, the request will fail with a <code>InvalidTransactionTimeout</code> error.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>int</td></tr> |
| <tr><th>Default:</th><td>60000 (1 minute)</td></tr> |
| <tr><th>Valid Values:</th><td></td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| <li> |
| <h4 class="anchor-heading"> |
| <a class="anchor-link" id="transactional.id"></a> |
| <a href="#transactional.id">transactional.id</a> |
| </h4> |
| <p>The TransactionalId to use for transactional delivery. This enables reliability semantics which span multiple producer sessions since it allows the client to guarantee that transactions using the same TransactionalId have been completed prior to starting any new transactions. If no TransactionalId is provided, then the producer is limited to idempotent delivery. If a TransactionalId is configured, <code>enable.idempotence</code> is implied. By default the TransactionId is not configured, which means transactions cannot be used. Note that, by default, transactions require a cluster of at least three brokers which is the recommended setting for production; for development you can change this, by adjusting broker setting <code>transaction.state.log.replication.factor</code>.</p> |
| <table><tbody> |
| <tr><th>Type:</th><td>string</td></tr> |
| <tr><th>Default:</th><td>null</td></tr> |
| <tr><th>Valid Values:</th><td>non-empty string</td></tr> |
| <tr><th>Importance:</th><td>low</td></tr> |
| </tbody></table> |
| </li> |
| </ul> |
| |
