kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lind...@apache.org
Subject [kafka-site] branch asf-site updated: Add generated configs for Kafka 2.1.0 RC1
Date Sat, 10 Nov 2018 00:11:32 GMT
This is an automated email from the ASF dual-hosted git repository.

lindong pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/kafka-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 072afe8  Add generated configs for Kafka 2.1.0 RC1
072afe8 is described below

commit 072afe8317005ef577dff660220e49609f875de7
Author: Dong Lin <lindong28@gmail.com>
AuthorDate: Fri Nov 9 16:10:24 2018 -0800

    Add generated configs for Kafka 2.1.0 RC1
---
 21/generated/admin_client_config.html     |  102 +
 21/generated/connect_config.html          |  176 +
 21/generated/connect_metrics.html         |  181 +
 21/generated/connect_transforms.html      |  228 +
 21/generated/consumer_config.html         |  140 +
 21/generated/consumer_metrics.html        |   79 +
 21/generated/kafka_config.html            |  392 ++
 21/generated/producer_config.html         |  134 +
 21/generated/producer_metrics.html        |   78 +
 21/generated/protocol_api_keys.html       |   91 +
 21/generated/protocol_errors.html         |   86 +
 21/generated/protocol_messages.html       | 7281 +++++++++++++++++++++++++++++
 21/generated/protocol_types.html          |   20 +
 21/generated/sink_connector_config.html   |   46 +
 21/generated/source_connector_config.html |   36 +
 21/generated/streams_config.html          |   88 +
 21/generated/topic_config.html            |   61 +
 17 files changed, 9219 insertions(+)

diff --git a/21/generated/admin_client_config.html b/21/generated/admin_client_config.html
index e69de29..2f20d86 100644
--- a/21/generated/admin_client_config.html
+++ b/21/generated/admin_client_config.html
@@ -0,0 +1,102 @@
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>bootstrap.servers</td></td><td>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&mdash;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 me [...]
+<tr>
+<td>ssl.key.password</td></td><td>The password of the private key in the key store file. This is optional for client.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.keystore.location</td></td><td>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.keystore.password</td></td><td>The store password for the key store file. This is optional for client and only needed if ssl.keystore.location is configured. </td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.truststore.location</td></td><td>The location of the trust store file. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.truststore.password</td></td><td>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.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>client.dns.lookup</td></td><td><p>Controls how the client uses DNS lookups.</p><p>If set to <code>use_all_dns_ips</code> then, when the lookup returns multiple IP addresses for a hostname, they will all be attempted to connect to before failing the connection. Applies to both bootstrap and advertised servers.</p><p>If the value is <code>resolve_canonical_bootstrap_servers_only</code> each entry will be resolved and expanded into a list of canonical names.</p></td></td><td>string</td> [...]
+<tr>
+<td>client.id</td></td><td>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.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>connections.max.idle.ms</td></td><td>Close idle connections after the number of milliseconds specified by this config.</td></td><td>long</td></td><td>300000</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>receive.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>65536</td></td><td>[-1,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>request.timeout.ms</td></td><td>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.</td></td><td>int</td></td><td>120000</td></td><td>[0,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.client.callback.handler.class</td></td><td>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.jaas.config</td></td><td>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- [...]
+<tr>
+<td>sasl.kerberos.service.name</td></td><td>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.login.callback.handler.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium [...]
+<tr>
+<td>sasl.login.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.mechanism</td></td><td>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</td></td><td>string</td></td><td>GSSAPI</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>security.protocol</td></td><td>Protocol used to communicate with brokers. Valid values are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL.</td></td><td>string</td></td><td>PLAINTEXT</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>send.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>131072</td></td><td>[-1,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.enabled.protocols</td></td><td>The list of protocols enabled for SSL connections.</td></td><td>list</td></td><td>TLSv1.2,TLSv1.1,TLSv1</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.keystore.type</td></td><td>The file format of the key store file. This is optional for client.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.protocol</td></td><td>The SSL protocol used to generate the SSLContext. Default setting is TLS, which is fine for most cases. Allowed values in recent JVMs are TLS, TLSv1.1 and TLSv1.2. SSL, SSLv2 and SSLv3 may be supported in older JVMs, but their usage is discouraged due to known security vulnerabilities.</td></td><td>string</td></td><td>TLS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.provider</td></td><td>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.truststore.type</td></td><td>The file format of the trust store file.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>metadata.max.age.ms</td></td><td>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.</td></td><td>long</td></td><td>300000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metric.reporters</td></td><td>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.</td></td><td>list</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.num.samples</td></td><td>The number of samples maintained to compute metrics.</td></td><td>int</td></td><td>2</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.recording.level</td></td><td>The highest recording level for metrics.</td></td><td>string</td></td><td>INFO</td></td><td>[INFO, DEBUG]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.sample.window.ms</td></td><td>The window of time a metrics sample is computed over.</td></td><td>long</td></td><td>30000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.max.ms</td></td><td>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.</td></td><td>long</td></td><td>1000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.ms</td></td><td>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.</td></td><td>long</td></td><td>50</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>retries</td></td><td>Setting a value greater than zero will cause the client to resend any request that fails with a potentially transient error.</td></td><td>int</td></td><td>5</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>retry.backoff.ms</td></td><td>The amount of time to wait before attempting to retry a failed request. This avoids repeatedly sending requests in a tight loop under some failure scenarios.</td></td><td>long</td></td><td>100</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.kinit.cmd</td></td><td>Kerberos kinit command path.</td></td><td>string</td></td><td>/usr/bin/kinit</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.min.time.before.relogin</td></td><td>Login thread sleep time between refresh attempts.</td></td><td>long</td></td><td>60000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.jitter</td></td><td>Percentage of random jitter added to the renewal time.</td></td><td>double</td></td><td>0.05</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.login.refresh.buffer.seconds</td></td><td>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.pe [...]
+<tr>
+<td>sasl.login.refresh.min.period.seconds</td></td><td>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.</td></td><td>short</td></td><td>60</td></td><td [...]
+<tr>
+<td>sasl.login.refresh.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td>[0.5,...,1.0]</td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.login.refresh.window.jitter</td></td><td>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.</td></td><td>double</td></td><td>0.05</td></td><td>[0.0,...,0.25]</td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.cipher.suites</td></td><td>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.</td></td><td>list</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.endpoint.identification.algorithm</td></td><td>The endpoint identification algorithm to validate server hostname using server certificate. </td></td><td>string</td></td><td>https</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.keymanager.algorithm</td></td><td>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>SunX509</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.secure.random.implementation</td></td><td>The SecureRandom PRNG implementation to use for SSL cryptography operations. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.trustmanager.algorithm</td></td><td>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>PKIX</td></td><td></td></td><td>low</td></td></tr>
+</tbody></table>
diff --git a/21/generated/connect_config.html b/21/generated/connect_config.html
index e69de29..e24e6ad 100644
--- a/21/generated/connect_config.html
+++ b/21/generated/connect_config.html
@@ -0,0 +1,176 @@
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>config.storage.topic</td></td><td>The name of the Kafka topic where connector configurations are stored</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>group.id</td></td><td>A unique string that identifies the Connect cluster group this worker belongs to.</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>key.converter</td></td><td>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</td></td><td>class</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>offset.storage.topic</td></td><td>The name of the Kafka topic where connector offsets are stored</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>status.storage.topic</td></td><td>The name of the Kafka topic where connector and task status are stored</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>value.converter</td></td><td>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</td></td><td>class</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>bootstrap.servers</td></td><td>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&mdash;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 me [...]
+<tr>
+<td>heartbeat.interval.ms</td></td><td>The expected time between heartbeats to the group coordinator when using Kafka's group management facilities. Heartbeats are used to ensure that the worker's session stays active and to facilitate rebalancing when new members join or leave the group. The value must be set lower than <code>session.timeout.ms</code>, but typically should be set no higher than 1/3 of that value. It can be adjusted even lower to control the expected time for normal reba [...]
+<tr>
+<td>rebalance.timeout.ms</td></td><td>The maximum allowed time for each worker to join the group once a rebalance has begun. This is basically a limit on the amount of time needed for all tasks to flush any pending data and commit offsets. If the timeout is exceeded, then the worker will be removed from the group, which will cause offset commit failures.</td></td><td>int</td></td><td>60000</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>session.timeout.ms</td></td><td>The timeout used to detect worker failures. The worker sends periodic heartbeats to indicate its liveness to the broker. If no heartbeats are received by the broker before the expiration of this session timeout, then the broker will remove the worker from the group and initiate a rebalance. Note that the value must be in the allowable range as configured in the broker configuration by <code>group.min.session.timeout.ms</code> and <code>group.max.sessio [...]
+<tr>
+<td>ssl.key.password</td></td><td>The password of the private key in the key store file. This is optional for client.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.keystore.location</td></td><td>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.keystore.password</td></td><td>The store password for the key store file. This is optional for client and only needed if ssl.keystore.location is configured. </td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.truststore.location</td></td><td>The location of the trust store file. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.truststore.password</td></td><td>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.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>client.dns.lookup</td></td><td><p>Controls how the client uses DNS lookups.</p><p>If set to <code>use_all_dns_ips</code> then, when the lookup returns multiple IP addresses for a hostname, they will all be attempted to connect to before failing the connection. Applies to both bootstrap and advertised servers.</p><p>If the value is <code>resolve_canonical_bootstrap_servers_only</code> each entry will be resolved and expanded into a list of canonical names.</p></td></td><td>string</td> [...]
+<tr>
+<td>connections.max.idle.ms</td></td><td>Close idle connections after the number of milliseconds specified by this config.</td></td><td>long</td></td><td>540000</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>receive.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>32768</td></td><td>[0,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>request.timeout.ms</td></td><td>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.</td></td><td>int</td></td><td>40000</td></td><td>[0,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.client.callback.handler.class</td></td><td>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.jaas.config</td></td><td>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- [...]
+<tr>
+<td>sasl.kerberos.service.name</td></td><td>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.login.callback.handler.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium [...]
+<tr>
+<td>sasl.login.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.mechanism</td></td><td>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</td></td><td>string</td></td><td>GSSAPI</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>security.protocol</td></td><td>Protocol used to communicate with brokers. Valid values are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL.</td></td><td>string</td></td><td>PLAINTEXT</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>send.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>131072</td></td><td>[0,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.enabled.protocols</td></td><td>The list of protocols enabled for SSL connections.</td></td><td>list</td></td><td>TLSv1.2,TLSv1.1,TLSv1</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.keystore.type</td></td><td>The file format of the key store file. This is optional for client.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.protocol</td></td><td>The SSL protocol used to generate the SSLContext. Default setting is TLS, which is fine for most cases. Allowed values in recent JVMs are TLS, TLSv1.1 and TLSv1.2. SSL, SSLv2 and SSLv3 may be supported in older JVMs, but their usage is discouraged due to known security vulnerabilities.</td></td><td>string</td></td><td>TLS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.provider</td></td><td>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.truststore.type</td></td><td>The file format of the trust store file.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>worker.sync.timeout.ms</td></td><td>When the worker is out of sync with other workers and needs to resynchronize configurations, wait up to this amount of time before giving up, leaving the group, and waiting a backoff period before rejoining.</td></td><td>int</td></td><td>3000</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>worker.unsync.backoff.ms</td></td><td>When the worker is out of sync with other workers and  fails to catch up within worker.sync.timeout.ms, leave the Connect cluster for this long before rejoining.</td></td><td>int</td></td><td>300000</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>access.control.allow.methods</td></td><td>Sets the methods supported for cross origin requests by setting the Access-Control-Allow-Methods header. The default value of the Access-Control-Allow-Methods header allows cross origin requests for GET, POST and HEAD.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>access.control.allow.origin</td></td><td>Value to set the Access-Control-Allow-Origin header to for REST API requests.To enable cross origin access, set this to the domain of the application that should be permitted to access the API, or '*' to allow access from any domain. The default value only allows access from the domain of the REST API.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>client.id</td></td><td>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.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>config.providers</td></td><td>Comma-separated names of <code>ConfigProvider</code> classes, loaded and used in the order specified. Implementing the interface  <code>ConfigProvider</code> allows you to replace variable references in connector configurations, such as for externalized secrets. </td></td><td>list</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>config.storage.replication.factor</td></td><td>Replication factor used when creating the configuration storage topic</td></td><td>short</td></td><td>3</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>header.converter</td></td><td>HeaderConverter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the header values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro. By default, the SimpleHeaderConverter is used to serialize header values to strings and deseria [...]
+<tr>
+<td>internal.key.converter</td></td><td>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro. This setting controls the format used for internal bookkeeping data used by the framework, such as confi [...]
+<tr>
+<td>internal.value.converter</td></td><td>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro. This setting controls the format used for internal bookkeeping data used by the framework, such as c [...]
+<tr>
+<td>listeners</td></td><td>List of comma-separated URIs the REST API will listen on. The supported protocols are HTTP and HTTPS.
+ Specify hostname as 0.0.0.0 to bind to all interfaces.
+ Leave hostname empty to bind to default interface.
+ Examples of legal listener lists: HTTP://myhost:8083,HTTPS://myhost:8084</td></td><td>list</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>metadata.max.age.ms</td></td><td>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.</td></td><td>long</td></td><td>300000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metric.reporters</td></td><td>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.</td></td><td>list</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.num.samples</td></td><td>The number of samples maintained to compute metrics.</td></td><td>int</td></td><td>2</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.recording.level</td></td><td>The highest recording level for metrics.</td></td><td>string</td></td><td>INFO</td></td><td>[INFO, DEBUG]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.sample.window.ms</td></td><td>The window of time a metrics sample is computed over.</td></td><td>long</td></td><td>30000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>offset.flush.interval.ms</td></td><td>Interval at which to try committing offsets for tasks.</td></td><td>long</td></td><td>60000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>offset.flush.timeout.ms</td></td><td>Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt.</td></td><td>long</td></td><td>5000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>offset.storage.partitions</td></td><td>The number of partitions used when creating the offset storage topic</td></td><td>int</td></td><td>25</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>offset.storage.replication.factor</td></td><td>Replication factor used when creating the offset storage topic</td></td><td>short</td></td><td>3</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>plugin.path</td></td><td>List of paths separated by commas (,) that contain plugins (connectors, converters, transformations). The list should consist of top level directories that include any combination of: 
+a) directories immediately containing jars with plugins and their dependencies
+b) uber-jars with plugins and their dependencies
+c) directories immediately containing the package directory structure of classes of plugins and their dependencies
+Note: symlinks will be followed to discover dependencies or plugins.
+Examples: plugin.path=/usr/local/share/java,/usr/local/share/kafka/plugins,/opt/connectors</td></td><td>list</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.max.ms</td></td><td>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.</td></td><td>long</td></td><td>1000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.ms</td></td><td>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.</td></td><td>long</td></td><td>50</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>rest.advertised.host.name</td></td><td>If this is set, this is the hostname that will be given out to other workers to connect to.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>rest.advertised.listener</td></td><td>Sets the advertised listener (HTTP or HTTPS) which will be given to other workers to use.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>rest.advertised.port</td></td><td>If this is set, this is the port that will be given out to other workers to connect to.</td></td><td>int</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>rest.extension.classes</td></td><td>Comma-separated names of <code>ConnectRestExtension</code> classes, loaded and called in the order specified. Implementing the interface  <code>ConnectRestExtension</code> allows you to inject into Connect's REST API user defined resources like filters. Typically used to add custom capability like logging, security, etc. </td></td><td>list</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>rest.host.name</td></td><td>Hostname for the REST API. If this is set, it will only bind to this interface.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>rest.port</td></td><td>Port for the REST API to listen on.</td></td><td>int</td></td><td>8083</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>retry.backoff.ms</td></td><td>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.</td></td><td>long</td></td><td>100</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.kinit.cmd</td></td><td>Kerberos kinit command path.</td></td><td>string</td></td><td>/usr/bin/kinit</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.min.time.before.relogin</td></td><td>Login thread sleep time between refresh attempts.</td></td><td>long</td></td><td>60000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.jitter</td></td><td>Percentage of random jitter added to the renewal time.</td></td><td>double</td></td><td>0.05</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.login.refresh.buffer.seconds</td></td><td>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.pe [...]
+<tr>
+<td>sasl.login.refresh.min.period.seconds</td></td><td>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.</td></td><td>short</td></td><td>60</td></td><td [...]
+<tr>
+<td>sasl.login.refresh.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td>[0.5,...,1.0]</td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.login.refresh.window.jitter</td></td><td>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.</td></td><td>double</td></td><td>0.05</td></td><td>[0.0,...,0.25]</td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.cipher.suites</td></td><td>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.</td></td><td>list</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.client.auth</td></td><td>Configures kafka broker to request client authentication. The following settings are common:  <ul> <li><code>ssl.client.auth=required</code> If set to required client authentication is required. <li><code>ssl.client.auth=requested</code> This means client authentication is optional. unlike requested , if this option is set client can choose not to provide authentication information about itself <li><code>ssl.client.auth=none</code> This means client authe [...]
+<tr>
+<td>ssl.endpoint.identification.algorithm</td></td><td>The endpoint identification algorithm to validate server hostname using server certificate. </td></td><td>string</td></td><td>https</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.keymanager.algorithm</td></td><td>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>SunX509</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.secure.random.implementation</td></td><td>The SecureRandom PRNG implementation to use for SSL cryptography operations. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.trustmanager.algorithm</td></td><td>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>PKIX</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>status.storage.partitions</td></td><td>The number of partitions used when creating the status storage topic</td></td><td>int</td></td><td>5</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>status.storage.replication.factor</td></td><td>Replication factor used when creating the status storage topic</td></td><td>short</td></td><td>3</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>task.shutdown.graceful.timeout.ms</td></td><td>Amount of time to wait for tasks to shutdown gracefully. This is the total amount of time, not per task. All task have shutdown triggered, then they are waited on sequentially.</td></td><td>long</td></td><td>5000</td></td><td></td></td><td>low</td></td></tr>
+</tbody></table>
diff --git a/21/generated/connect_metrics.html b/21/generated/connect_metrics.html
index e69de29..8b5b27e 100644
--- a/21/generated/connect_metrics.html
+++ b/21/generated/connect_metrics.html
@@ -0,0 +1,181 @@
+<table class="data-table"><tbody>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.connect:type=connect-worker-metrics</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>connector-count</td><td>The number of connectors run in this worker.</td></tr>
+<tr>
+<td></td><td>connector-startup-attempts-total</td><td>The total number of connector startups that this worker has attempted.</td></tr>
+<tr>
+<td></td><td>connector-startup-failure-percentage</td><td>The average percentage of this worker's connectors starts that failed.</td></tr>
+<tr>
+<td></td><td>connector-startup-failure-total</td><td>The total number of connector starts that failed.</td></tr>
+<tr>
+<td></td><td>connector-startup-success-percentage</td><td>The average percentage of this worker's connectors starts that succeeded.</td></tr>
+<tr>
+<td></td><td>connector-startup-success-total</td><td>The total number of connector starts that succeeded.</td></tr>
+<tr>
+<td></td><td>task-count</td><td>The number of tasks run in this worker.</td></tr>
+<tr>
+<td></td><td>task-startup-attempts-total</td><td>The total number of task startups that this worker has attempted.</td></tr>
+<tr>
+<td></td><td>task-startup-failure-percentage</td><td>The average percentage of this worker's tasks starts that failed.</td></tr>
+<tr>
+<td></td><td>task-startup-failure-total</td><td>The total number of task starts that failed.</td></tr>
+<tr>
+<td></td><td>task-startup-success-percentage</td><td>The average percentage of this worker's tasks starts that succeeded.</td></tr>
+<tr>
+<td></td><td>task-startup-success-total</td><td>The total number of task starts that succeeded.</td></tr>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.connect:type=connect-worker-rebalance-metrics</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>completed-rebalances-total</td><td>The total number of rebalances completed by this worker.</td></tr>
+<tr>
+<td></td><td>epoch</td><td>The epoch or generation number of this worker.</td></tr>
+<tr>
+<td></td><td>leader-name</td><td>The name of the group leader.</td></tr>
+<tr>
+<td></td><td>rebalance-avg-time-ms</td><td>The average time in milliseconds spent by this worker to rebalance.</td></tr>
+<tr>
+<td></td><td>rebalance-max-time-ms</td><td>The maximum time in milliseconds spent by this worker to rebalance.</td></tr>
+<tr>
+<td></td><td>rebalancing</td><td>Whether this worker is currently rebalancing.</td></tr>
+<tr>
+<td></td><td>time-since-last-rebalance-ms</td><td>The time in milliseconds since this worker completed the most recent rebalance.</td></tr>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.connect:type=connector-metrics,connector="{connector}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>connector-class</td><td>The name of the connector class.</td></tr>
+<tr>
+<td></td><td>connector-type</td><td>The type of the connector. One of 'source' or 'sink'.</td></tr>
+<tr>
+<td></td><td>connector-version</td><td>The version of the connector class, as reported by the connector.</td></tr>
+<tr>
+<td></td><td>status</td><td>The status of the connector. One of 'unassigned', 'running', 'paused', 'failed', or 'destroyed'.</td></tr>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>batch-size-avg</td><td>The average size of the batches processed by the connector.</td></tr>
+<tr>
+<td></td><td>batch-size-max</td><td>The maximum size of the batches processed by the connector.</td></tr>
+<tr>
+<td></td><td>offset-commit-avg-time-ms</td><td>The average time in milliseconds taken by this task to commit offsets.</td></tr>
+<tr>
+<td></td><td>offset-commit-failure-percentage</td><td>The average percentage of this task's offset commit attempts that failed.</td></tr>
+<tr>
+<td></td><td>offset-commit-max-time-ms</td><td>The maximum time in milliseconds taken by this task to commit offsets.</td></tr>
+<tr>
+<td></td><td>offset-commit-success-percentage</td><td>The average percentage of this task's offset commit attempts that succeeded.</td></tr>
+<tr>
+<td></td><td>pause-ratio</td><td>The fraction of time this task has spent in the pause state.</td></tr>
+<tr>
+<td></td><td>running-ratio</td><td>The fraction of time this task has spent in the running state.</td></tr>
+<tr>
+<td></td><td>status</td><td>The status of the connector task. One of 'unassigned', 'running', 'paused', 'failed', or 'destroyed'.</td></tr>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>offset-commit-completion-rate</td><td>The average per-second number of offset commit completions that were completed successfully.</td></tr>
+<tr>
+<td></td><td>offset-commit-completion-total</td><td>The total number of offset commit completions that were completed successfully.</td></tr>
+<tr>
+<td></td><td>offset-commit-seq-no</td><td>The current sequence number for offset commits.</td></tr>
+<tr>
+<td></td><td>offset-commit-skip-rate</td><td>The average per-second number of offset commit completions that were received too late and skipped/ignored.</td></tr>
+<tr>
+<td></td><td>offset-commit-skip-total</td><td>The total number of offset commit completions that were received too late and skipped/ignored.</td></tr>
+<tr>
+<td></td><td>partition-count</td><td>The number of topic partitions assigned to this task belonging to the named sink connector in this worker.</td></tr>
+<tr>
+<td></td><td>put-batch-avg-time-ms</td><td>The average time taken by this task to put a batch of sinks records.</td></tr>
+<tr>
+<td></td><td>put-batch-max-time-ms</td><td>The maximum time taken by this task to put a batch of sinks records.</td></tr>
+<tr>
+<td></td><td>sink-record-active-count</td><td>The number of records that have been read from Kafka but not yet completely committed/flushed/acknowledged by the sink task.</td></tr>
+<tr>
+<td></td><td>sink-record-active-count-avg</td><td>The average number of records that have been read from Kafka but not yet completely committed/flushed/acknowledged by the sink task.</td></tr>
+<tr>
+<td></td><td>sink-record-active-count-max</td><td>The maximum number of records that have been read from Kafka but not yet completely committed/flushed/acknowledged by the sink task.</td></tr>
+<tr>
+<td></td><td>sink-record-lag-max</td><td>The maximum lag in terms of number of records that the sink task is behind the consumer's position for any topic partitions.</td></tr>
+<tr>
+<td></td><td>sink-record-read-rate</td><td>The average per-second number of records read from Kafka for this task belonging to the named sink connector in this worker. This is before transformations are applied.</td></tr>
+<tr>
+<td></td><td>sink-record-read-total</td><td>The total number of records read from Kafka by this task belonging to the named sink connector in this worker, since the task was last restarted.</td></tr>
+<tr>
+<td></td><td>sink-record-send-rate</td><td>The average per-second number of records output from the transformations and sent/put to this task belonging to the named sink connector in this worker. This is after transformations are applied and excludes any records filtered out by the transformations.</td></tr>
+<tr>
+<td></td><td>sink-record-send-total</td><td>The total number of records output from the transformations and sent/put to this task belonging to the named sink connector in this worker, since the task was last restarted.</td></tr>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>poll-batch-avg-time-ms</td><td>The average time in milliseconds taken by this task to poll for a batch of source records.</td></tr>
+<tr>
+<td></td><td>poll-batch-max-time-ms</td><td>The maximum time in milliseconds taken by this task to poll for a batch of source records.</td></tr>
+<tr>
+<td></td><td>source-record-active-count</td><td>The number of records that have been produced by this task but not yet completely written to Kafka.</td></tr>
+<tr>
+<td></td><td>source-record-active-count-avg</td><td>The average number of records that have been produced by this task but not yet completely written to Kafka.</td></tr>
+<tr>
+<td></td><td>source-record-active-count-max</td><td>The maximum number of records that have been produced by this task but not yet completely written to Kafka.</td></tr>
+<tr>
+<td></td><td>source-record-poll-rate</td><td>The average per-second number of records produced/polled (before transformation) by this task belonging to the named source connector in this worker.</td></tr>
+<tr>
+<td></td><td>source-record-poll-total</td><td>The total number of records produced/polled (before transformation) by this task belonging to the named source connector in this worker.</td></tr>
+<tr>
+<td></td><td>source-record-write-rate</td><td>The average per-second number of records output from the transformations and written to Kafka for this task belonging to the named source connector in this worker. This is after transformations are applied and excludes any records filtered out by the transformations.</td></tr>
+<tr>
+<td></td><td>source-record-write-total</td><td>The number of records output from the transformations and written to Kafka for this task belonging to the named source connector in this worker, since the task was last restarted.</td></tr>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>deadletterqueue-produce-failures</td><td>The number of failed writes to the dead letter queue.</td></tr>
+<tr>
+<td></td><td>deadletterqueue-produce-requests</td><td>The number of attempted writes to the dead letter queue.</td></tr>
+<tr>
+<td></td><td>last-error-timestamp</td><td>The epoch timestamp when this task last encountered an error.</td></tr>
+<tr>
+<td></td><td>total-errors-logged</td><td>The number of errors that were logged.</td></tr>
+<tr>
+<td></td><td>total-record-errors</td><td>The number of record processing errors in this task. </td></tr>
+<tr>
+<td></td><td>total-record-failures</td><td>The number of record processing failures in this task.</td></tr>
+<tr>
+<td></td><td>total-records-skipped</td><td>The number of records skipped due to errors.</td></tr>
+<tr>
+<td></td><td>total-retries</td><td>The number of operations retried.</td></tr>
+</tbody></table>
diff --git a/21/generated/connect_transforms.html b/21/generated/connect_transforms.html
index e69de29..452ab01 100644
--- a/21/generated/connect_transforms.html
+++ b/21/generated/connect_transforms.html
@@ -0,0 +1,228 @@
+<div id="org.apache.kafka.connect.transforms.InsertField">
+<h5>org.apache.kafka.connect.transforms.InsertField</h5>
+Insert field(s) using attributes from the record metadata or a configured static value.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.InsertField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.InsertField$Value</code>).
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>offset.field</td></td><td>Field name for Kafka offset - only applicable to sink connectors.<br/>Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>partition.field</td></td><td>Field name for Kafka partition. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>static.field</td></td><td>Field name for static data field. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>static.value</td></td><td>Static field value, if field name configured.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>timestamp.field</td></td><td>Field name for record timestamp. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>topic.field</td></td><td>Field name for Kafka topic. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.ReplaceField">
+<h5>org.apache.kafka.connect.transforms.ReplaceField</h5>
+Filter or rename fields.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.ReplaceField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.ReplaceField$Value</code>).
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>blacklist</td></td><td>Fields to exclude. This takes precedence over the whitelist.</td></td><td>list</td></td><td>""</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>renames</td></td><td>Field rename mappings.</td></td><td>list</td></td><td>""</td></td><td>list of colon-delimited pairs, e.g. <code>foo:bar,abc:xyz</code></td></td><td>medium</td></td></tr>
+<tr>
+<td>whitelist</td></td><td>Fields to include. If specified, only these fields will be used.</td></td><td>list</td></td><td>""</td></td><td></td></td><td>medium</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.MaskField">
+<h5>org.apache.kafka.connect.transforms.MaskField</h5>
+Mask specified fields with a valid null value for the field type (i.e. 0, false, empty string, and so on).<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.MaskField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.MaskField$Value</code>).
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>fields</td></td><td>Names of fields to mask.</td></td><td>list</td></td><td></td></td><td>non-empty list</td></td><td>high</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.ValueToKey">
+<h5>org.apache.kafka.connect.transforms.ValueToKey</h5>
+Replace the record key with a new key formed from a subset of fields in the record value.
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>fields</td></td><td>Field names on the record value to extract as the record key.</td></td><td>list</td></td><td></td></td><td>non-empty list</td></td><td>high</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.HoistField">
+<h5>org.apache.kafka.connect.transforms.HoistField</h5>
+Wrap data using the specified field name in a Struct when schema present, or a Map in the case of schemaless data.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.HoistField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.HoistField$Value</code>).
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>field</td></td><td>Field name for the single field that will be created in the resulting Struct or Map.</td></td><td>string</td></td><td></td></td><td></td></td><td>medium</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.ExtractField">
+<h5>org.apache.kafka.connect.transforms.ExtractField</h5>
+Extract the specified field from a Struct when schema present, or a Map in the case of schemaless data. Any null values are passed through unmodified.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.ExtractField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.ExtractField$Value</code>).
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>field</td></td><td>Field name to extract.</td></td><td>string</td></td><td></td></td><td></td></td><td>medium</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.SetSchemaMetadata">
+<h5>org.apache.kafka.connect.transforms.SetSchemaMetadata</h5>
+Set the schema name, version or both on the record's key (<code>org.apache.kafka.connect.transforms.SetSchemaMetadata$Key</code>) or value (<code>org.apache.kafka.connect.transforms.SetSchemaMetadata$Value</code>) schema.
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>schema.name</td></td><td>Schema name to set.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>schema.version</td></td><td>Schema version to set.</td></td><td>int</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.TimestampRouter">
+<h5>org.apache.kafka.connect.transforms.TimestampRouter</h5>
+Update the record's topic field as a function of the original topic value and the record timestamp.<p/>This is mainly useful for sink connectors, since the topic field is often used to determine the equivalent entity name in the destination system(e.g. database table or search index name).
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>timestamp.format</td></td><td>Format string for the timestamp that is compatible with <code>java.text.SimpleDateFormat</code>.</td></td><td>string</td></td><td>yyyyMMdd</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>topic.format</td></td><td>Format string which can contain <code>${topic}</code> and <code>${timestamp}</code> as placeholders for the topic and timestamp, respectively.</td></td><td>string</td></td><td>${topic}-${timestamp}</td></td><td></td></td><td>high</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.RegexRouter">
+<h5>org.apache.kafka.connect.transforms.RegexRouter</h5>
+Update the record topic using the configured regular expression and replacement string.<p/>Under the hood, the regex is compiled to a <code>java.util.regex.Pattern</code>. If the pattern matches the input topic, <code>java.util.regex.Matcher#replaceFirst()</code> is used with the replacement string to obtain the new topic.
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>regex</td></td><td>Regular expression to use for matching.</td></td><td>string</td></td><td></td></td><td>valid regex</td></td><td>high</td></td></tr>
+<tr>
+<td>replacement</td></td><td>Replacement string.</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.Flatten">
+<h5>org.apache.kafka.connect.transforms.Flatten</h5>
+Flatten a nested data structure, generating names for each field by concatenating the field names at each level with a configurable delimiter character. Applies to Struct when schema present, or a Map in the case of schemaless data. The default delimiter is '.'.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.Flatten$Key</code>) or value (<code>org.apache.kafka.connect.transforms.Flatten$Value</code>).
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>delimiter</td></td><td>Delimiter to insert between field names from the input record when generating field names for the output record</td></td><td>string</td></td><td>.</td></td><td></td></td><td>medium</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.Cast">
+<h5>org.apache.kafka.connect.transforms.Cast</h5>
+Cast fields or the entire key or value to a specific type, e.g. to force an integer field to a smaller width. Only simple primitive types are supported -- integers, floats, boolean, and string. <p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.Cast$Key</code>) or value (<code>org.apache.kafka.connect.transforms.Cast$Value</code>).
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>spec</td></td><td>List of fields and the type to cast them to of the form field1:type,field2:type to cast fields of Maps or Structs. A single type to cast the entire value. Valid types are int8, int16, int32, int64, float32, float64, boolean, and string.</td></td><td>list</td></td><td></td></td><td>list of colon-delimited pairs, e.g. <code>foo:bar,abc:xyz</code></td></td><td>high</td></td></tr>
+</tbody></table>
+</div>
+<div id="org.apache.kafka.connect.transforms.TimestampConverter">
+<h5>org.apache.kafka.connect.transforms.TimestampConverter</h5>
+Convert timestamps between different formats such as Unix epoch, strings, and Connect Date/Timestamp types.Applies to individual fields or to the entire value.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.TimestampConverter$Key</code>) or value (<code>org.apache.kafka.connect.transforms.TimestampConverter$Value</code>).
+<p/>
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>target.type</td></td><td>The desired timestamp representation: string, unix, Date, Time, or Timestamp</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>field</td></td><td>The field containing the timestamp, or empty if the entire value is a timestamp</td></td><td>string</td></td><td>""</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>format</td></td><td>A SimpleDateFormat-compatible format for the timestamp. Used to generate the output when type=string or used to parse the input if the input is a string.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>medium</td></td></tr>
+</tbody></table>
+</div>
diff --git a/21/generated/consumer_config.html b/21/generated/consumer_config.html
index e69de29..64b3059 100644
--- a/21/generated/consumer_config.html
+++ b/21/generated/consumer_config.html
@@ -0,0 +1,140 @@
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>key.deserializer</td></td><td>Deserializer class for key that implements the <code>org.apache.kafka.common.serialization.Deserializer</code> interface.</td></td><td>class</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>value.deserializer</td></td><td>Deserializer class for value that implements the <code>org.apache.kafka.common.serialization.Deserializer</code> interface.</td></td><td>class</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>bootstrap.servers</td></td><td>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&mdash;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 me [...]
+<tr>
+<td>fetch.min.bytes</td></td><td>The minimum amount of data the server should return for a fetch request. If insufficient data is available the request will wait for that much data to accumulate before answering the request. The default setting of 1 byte means that fetch requests are answered as soon as a single byte of data is available or the fetch request times out waiting for data to arrive. Setting this to something greater than 1 will cause the server to wait for larger amounts of  [...]
+<tr>
+<td>group.id</td></td><td>A unique string that identifies the consumer group this consumer belongs to. This property is required if the consumer uses either the group management functionality by using <code>subscribe(topic)</code> or the Kafka-based offset management strategy.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>heartbeat.interval.ms</td></td><td>The expected time between heartbeats to the consumer coordinator when using Kafka's group management facilities. Heartbeats are used to ensure that the consumer's session stays active and to facilitate rebalancing when new consumers join or leave the group. The value must be set lower than <code>session.timeout.ms</code>, but typically should be set no higher than 1/3 of that value. It can be adjusted even lower to control the expected time for norm [...]
+<tr>
+<td>max.partition.fetch.bytes</td></td><td>The maximum amount of data per-partition the server will return. Records are fetched in batches by the consumer. If the first record batch in the first non-empty partition of the fetch is larger than this limit, the batch will still be returned to ensure that the consumer can make progress. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker config) or <code>max.message.bytes</code> (topic c [...]
+<tr>
+<td>session.timeout.ms</td></td><td>The timeout used to detect consumer failures when using Kafka's group management facility. The consumer sends periodic heartbeats to indicate its liveness to the broker. If no heartbeats are received by the broker before the expiration of this session timeout, then the broker will remove this consumer from the group and initiate a rebalance. Note that the value must be in the allowable range as configured in the broker configuration by <code>group.min. [...]
+<tr>
+<td>ssl.key.password</td></td><td>The password of the private key in the key store file. This is optional for client.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.keystore.location</td></td><td>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.keystore.password</td></td><td>The store password for the key store file. This is optional for client and only needed if ssl.keystore.location is configured. </td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.truststore.location</td></td><td>The location of the trust store file. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.truststore.password</td></td><td>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.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>auto.offset.reset</td></td><td>What to do when there is no initial offset in Kafka or if the current offset does not exist any more on the server (e.g. because that data has been deleted): <ul><li>earliest: automatically reset the offset to the earliest offset<li>latest: automatically reset the offset to the latest offset</li><li>none: throw exception to the consumer if no previous offset is found for the consumer's group</li><li>anything else: throw exception to the consumer.</li></ [...]
+<tr>
+<td>client.dns.lookup</td></td><td><p>Controls how the client uses DNS lookups.</p><p>If set to <code>use_all_dns_ips</code> then, when the lookup returns multiple IP addresses for a hostname, they will all be attempted to connect to before failing the connection. Applies to both bootstrap and advertised servers.</p><p>If the value is <code>resolve_canonical_bootstrap_servers_only</code> each entry will be resolved and expanded into a list of canonical names.</p></td></td><td>string</td> [...]
+<tr>
+<td>connections.max.idle.ms</td></td><td>Close idle connections after the number of milliseconds specified by this config.</td></td><td>long</td></td><td>540000</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>default.api.timeout.ms</td></td><td>Specifies the timeout (in milliseconds) for consumer APIs that could block. This configuration is used as the default timeout for all consumer operations that do not explicitly accept a <code>timeout</code> parameter.</td></td><td>int</td></td><td>60000</td></td><td>[0,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>enable.auto.commit</td></td><td>If true the consumer's offset will be periodically committed in the background.</td></td><td>boolean</td></td><td>true</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>exclude.internal.topics</td></td><td>Whether records from internal topics (such as offsets) should be exposed to the consumer. If set to <code>true</code> the only way to receive records from an internal topic is subscribing to it.</td></td><td>boolean</td></td><td>true</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>fetch.max.bytes</td></td><td>The maximum amount of data the server should return for a fetch request. Records are fetched in batches by the consumer, and if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that the consumer can make progress. As such, this is not a absolute maximum. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker  [...]
+<tr>
+<td>isolation.level</td></td><td><p>Controls how to read messages written transactionally. If set to <code>read_committed</code>, consumer.poll() will only return transactional messages which have been committed. If set to <code>read_uncommitted</code>' (the default), consumer.poll() will return all messages, even transactional messages which have been aborted. Non-transactional messages will be returned unconditionally in either mode.</p> <p>Messages will always be returned in offset or [...]
+<tr>
+<td>max.poll.interval.ms</td></td><td>The maximum delay between invocations of poll() when using consumer group management. This places an upper bound on the amount of time that the consumer can be idle before fetching more records. If poll() is not called before expiration of this timeout, then the consumer is considered failed and the group will rebalance in order to reassign the partitions to another member. </td></td><td>int</td></td><td>300000</td></td><td>[1,...]</td></td><td>mediu [...]
+<tr>
+<td>max.poll.records</td></td><td>The maximum number of records returned in a single call to poll().</td></td><td>int</td></td><td>500</td></td><td>[1,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>partition.assignment.strategy</td></td><td>The class name of the partition assignment strategy that the client will use to distribute partition ownership amongst consumer instances when group management is used</td></td><td>list</td></td><td>class org.apache.kafka.clients.consumer.RangeAssignor</td></td><td>non-null string</td></td><td>medium</td></td></tr>
+<tr>
+<td>receive.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>65536</td></td><td>[-1,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>request.timeout.ms</td></td><td>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.</td></td><td>int</td></td><td>30000</td></td><td>[0,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.client.callback.handler.class</td></td><td>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.jaas.config</td></td><td>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- [...]
+<tr>
+<td>sasl.kerberos.service.name</td></td><td>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.login.callback.handler.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium [...]
+<tr>
+<td>sasl.login.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.mechanism</td></td><td>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</td></td><td>string</td></td><td>GSSAPI</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>security.protocol</td></td><td>Protocol used to communicate with brokers. Valid values are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL.</td></td><td>string</td></td><td>PLAINTEXT</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>send.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>131072</td></td><td>[-1,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.enabled.protocols</td></td><td>The list of protocols enabled for SSL connections.</td></td><td>list</td></td><td>TLSv1.2,TLSv1.1,TLSv1</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.keystore.type</td></td><td>The file format of the key store file. This is optional for client.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.protocol</td></td><td>The SSL protocol used to generate the SSLContext. Default setting is TLS, which is fine for most cases. Allowed values in recent JVMs are TLS, TLSv1.1 and TLSv1.2. SSL, SSLv2 and SSLv3 may be supported in older JVMs, but their usage is discouraged due to known security vulnerabilities.</td></td><td>string</td></td><td>TLS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.provider</td></td><td>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.truststore.type</td></td><td>The file format of the trust store file.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>auto.commit.interval.ms</td></td><td>The frequency in milliseconds that the consumer offsets are auto-committed to Kafka if <code>enable.auto.commit</code> is set to <code>true</code>.</td></td><td>int</td></td><td>5000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>check.crcs</td></td><td>Automatically check the CRC32 of the records consumed. This ensures no on-the-wire or on-disk corruption to the messages occurred. This check adds some overhead, so it may be disabled in cases seeking extreme performance.</td></td><td>boolean</td></td><td>true</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>client.id</td></td><td>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.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>fetch.max.wait.ms</td></td><td>The maximum amount of time the server will block before answering the fetch request if there isn't sufficient data to immediately satisfy the requirement given by fetch.min.bytes.</td></td><td>int</td></td><td>500</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>interceptor.classes</td></td><td>A list of classes to use as interceptors. Implementing the <code>org.apache.kafka.clients.consumer.ConsumerInterceptor</code> interface allows you to intercept (and possibly mutate) records received by the consumer. By default, there are no interceptors.</td></td><td>list</td></td><td>""</td></td><td>non-null string</td></td><td>low</td></td></tr>
+<tr>
+<td>metadata.max.age.ms</td></td><td>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.</td></td><td>long</td></td><td>300000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metric.reporters</td></td><td>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.</td></td><td>list</td></td><td>""</td></td><td>non-null string</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.num.samples</td></td><td>The number of samples maintained to compute metrics.</td></td><td>int</td></td><td>2</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.recording.level</td></td><td>The highest recording level for metrics.</td></td><td>string</td></td><td>INFO</td></td><td>[INFO, DEBUG]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.sample.window.ms</td></td><td>The window of time a metrics sample is computed over.</td></td><td>long</td></td><td>30000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.max.ms</td></td><td>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.</td></td><td>long</td></td><td>1000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.ms</td></td><td>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.</td></td><td>long</td></td><td>50</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>retry.backoff.ms</td></td><td>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.</td></td><td>long</td></td><td>100</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.kinit.cmd</td></td><td>Kerberos kinit command path.</td></td><td>string</td></td><td>/usr/bin/kinit</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.min.time.before.relogin</td></td><td>Login thread sleep time between refresh attempts.</td></td><td>long</td></td><td>60000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.jitter</td></td><td>Percentage of random jitter added to the renewal time.</td></td><td>double</td></td><td>0.05</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.login.refresh.buffer.seconds</td></td><td>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.pe [...]
+<tr>
+<td>sasl.login.refresh.min.period.seconds</td></td><td>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.</td></td><td>short</td></td><td>60</td></td><td [...]
+<tr>
+<td>sasl.login.refresh.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td>[0.5,...,1.0]</td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.login.refresh.window.jitter</td></td><td>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.</td></td><td>double</td></td><td>0.05</td></td><td>[0.0,...,0.25]</td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.cipher.suites</td></td><td>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.</td></td><td>list</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.endpoint.identification.algorithm</td></td><td>The endpoint identification algorithm to validate server hostname using server certificate. </td></td><td>string</td></td><td>https</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.keymanager.algorithm</td></td><td>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>SunX509</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.secure.random.implementation</td></td><td>The SecureRandom PRNG implementation to use for SSL cryptography operations. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.trustmanager.algorithm</td></td><td>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>PKIX</td></td><td></td></td><td>low</td></td></tr>
+</tbody></table>
diff --git a/21/generated/consumer_metrics.html b/21/generated/consumer_metrics.html
index e69de29..7844d67 100644
--- a/21/generated/consumer_metrics.html
+++ b/21/generated/consumer_metrics.html
@@ -0,0 +1,79 @@
+<table class="data-table"><tbody>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>bytes-consumed-rate</td><td>The average number of bytes consumed per second</td></tr>
+<tr>
+<td></td><td>bytes-consumed-total</td><td>The total number of bytes consumed</td></tr>
+<tr>
+<td></td><td>fetch-latency-avg</td><td>The average time taken for a fetch request.</td></tr>
+<tr>
+<td></td><td>fetch-latency-max</td><td>The max time taken for any fetch request.</td></tr>
+<tr>
+<td></td><td>fetch-rate</td><td>The number of fetch requests per second.</td></tr>
+<tr>
+<td></td><td>fetch-size-avg</td><td>The average number of bytes fetched per request</td></tr>
+<tr>
+<td></td><td>fetch-size-max</td><td>The maximum number of bytes fetched per request</td></tr>
+<tr>
+<td></td><td>fetch-throttle-time-avg</td><td>The average throttle time in ms</td></tr>
+<tr>
+<td></td><td>fetch-throttle-time-max</td><td>The maximum throttle time in ms</td></tr>
+<tr>
+<td></td><td>fetch-total</td><td>The total number of fetch requests.</td></tr>
+<tr>
+<td></td><td>records-consumed-rate</td><td>The average number of records consumed per second</td></tr>
+<tr>
+<td></td><td>records-consumed-total</td><td>The total number of records consumed</td></tr>
+<tr>
+<td></td><td>records-lag-max</td><td>The maximum lag in terms of number of records for any partition in this window</td></tr>
+<tr>
+<td></td><td>records-lead-min</td><td>The minimum lead in terms of number of records for any partition in this window</td></tr>
+<tr>
+<td></td><td>records-per-request-avg</td><td>The average number of records in each request</td></tr>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}",topic="{topic}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>bytes-consumed-rate</td><td>The average number of bytes consumed per second for a topic</td></tr>
+<tr>
+<td></td><td>bytes-consumed-total</td><td>The total number of bytes consumed for a topic</td></tr>
+<tr>
+<td></td><td>fetch-size-avg</td><td>The average number of bytes fetched per request for a topic</td></tr>
+<tr>
+<td></td><td>fetch-size-max</td><td>The maximum number of bytes fetched per request for a topic</td></tr>
+<tr>
+<td></td><td>records-consumed-rate</td><td>The average number of records consumed per second for a topic</td></tr>
+<tr>
+<td></td><td>records-consumed-total</td><td>The total number of records consumed for a topic</td></tr>
+<tr>
+<td></td><td>records-per-request-avg</td><td>The average number of records in each request for a topic</td></tr>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.consumer:type=consumer-fetch-manager-metrics,partition="{partition}",topic="{topic}",client-id="{client-id}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>records-lag</td><td>The latest lag of the partition</td></tr>
+<tr>
+<td></td><td>records-lag-avg</td><td>The average lag of the partition</td></tr>
+<tr>
+<td></td><td>records-lag-max</td><td>The max lag of the partition</td></tr>
+<tr>
+<td></td><td>records-lead</td><td>The latest lead of the partition</td></tr>
+<tr>
+<td></td><td>records-lead-avg</td><td>The average lead of the partition</td></tr>
+<tr>
+<td></td><td>records-lead-min</td><td>The min lead of the partition</td></tr>
+</tbody></table>
diff --git a/21/generated/kafka_config.html b/21/generated/kafka_config.html
index e69de29..8be1583 100644
--- a/21/generated/kafka_config.html
+++ b/21/generated/kafka_config.html
@@ -0,0 +1,392 @@
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+<th>Dynamic Update Mode</th>
+</tr>
+<tr>
+<td>zookeeper.connect</td></td><td>Specifies the ZooKeeper connection string in the form <code>hostname:port</code> where host and port are the host and port of a ZooKeeper server. To allow connecting through other ZooKeeper nodes when that ZooKeeper machine is down you can also specify multiple hosts in the form <code>hostname1:port1,hostname2:port2,hostname3:port3</code>.
+The server can also have a ZooKeeper chroot path as part of its ZooKeeper connection string which puts its data under some path in the global ZooKeeper namespace. For example to give a chroot path of <code>/chroot/path</code> you would give the connection string as <code>hostname1:port1,hostname2:port2,hostname3:port3/chroot/path</code>.</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>advertised.host.name</td></td><td>DEPRECATED: only used when <code>advertised.listeners</code> or <code>listeners</code> are not set. Use <code>advertised.listeners</code> instead. 
+Hostname to publish to ZooKeeper for clients to use. In IaaS environments, this may need to be different from the interface to which the broker binds. If this is not set, it will use the value for <code>host.name</code> if configured. Otherwise it will use the value returned from java.net.InetAddress.getCanonicalHostName().</td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>advertised.listeners</td></td><td>Listeners to publish to ZooKeeper for clients to use, if different than the <code>listeners</code> config property. In IaaS environments, this may need to be different from the interface to which the broker binds. If this is not set, the value for <code>listeners</code> will be used. Unlike <code>listeners</code> it is not valid to advertise the 0.0.0.0 meta-address.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td><td>p [...]
+<tr>
+<td>advertised.port</td></td><td>DEPRECATED: only used when <code>advertised.listeners</code> or <code>listeners</code> are not set. Use <code>advertised.listeners</code> instead. 
+The port to publish to ZooKeeper for clients to use. In IaaS environments, this may need to be different from the port to which the broker binds. If this is not set, it will publish the same port that the broker binds to.</td></td><td>int</td></td><td>null</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>auto.create.topics.enable</td></td><td>Enable auto creation of topic on the server</td></td><td>boolean</td></td><td>true</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>auto.leader.rebalance.enable</td></td><td>Enables auto leader balancing. A background thread checks and triggers leader balance if required at regular intervals</td></td><td>boolean</td></td><td>true</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>background.threads</td></td><td>The number of threads to use for various background processing tasks</td></td><td>int</td></td><td>10</td></td><td>[1,...]</td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>broker.id</td></td><td>The broker id for this server. If unset, a unique broker id will be generated.To avoid conflicts between zookeeper generated broker id's and user configured broker id's, generated broker ids start from reserved.broker.max.id + 1.</td></td><td>int</td></td><td>-1</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>compression.type</td></td><td>Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer.</td></td><td>string</td></td><td>producer</td></td><td></td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>delete.topic.enable</td></td><td>Enables delete topic. Delete topic through the admin tool will have no effect if this config is turned off</td></td><td>boolean</td></td><td>true</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>host.name</td></td><td>DEPRECATED: only used when <code>listeners</code> is not set. Use <code>listeners</code> instead. 
+hostname of broker. If this is set, it will only bind to this address. If this is not set, it will bind to all interfaces</td></td><td>string</td></td><td>""</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>leader.imbalance.check.interval.seconds</td></td><td>The frequency with which the partition rebalance check is triggered by the controller</td></td><td>long</td></td><td>300</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>leader.imbalance.per.broker.percentage</td></td><td>The ratio of leader imbalance allowed per broker. The controller would trigger a leader balance if it goes above this value per broker. The value is specified in percentage.</td></td><td>int</td></td><td>10</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>listeners</td></td><td>Listener List - Comma-separated list of URIs we will listen on and the listener names. If the listener name is not a security protocol, listener.security.protocol.map must also be set.
+ Specify hostname as 0.0.0.0 to bind to all interfaces.
+ Leave hostname empty to bind to default interface.
+ Examples of legal listener lists:
+ PLAINTEXT://myhost:9092,SSL://:9091
+ CLIENT://0.0.0.0:9092,REPLICATION://localhost:9093
+</td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td><td>per-broker</td></tr>
+<tr>
+<td>log.dir</td></td><td>The directory in which the log data is kept (supplemental for log.dirs property)</td></td><td>string</td></td><td>/tmp/kafka-logs</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>log.dirs</td></td><td>The directories in which the log data is kept. If not set, the value in log.dir is used</td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>log.flush.interval.messages</td></td><td>The number of messages accumulated on a log partition before messages are flushed to disk </td></td><td>long</td></td><td>9223372036854775807</td></td><td>[1,...]</td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.flush.interval.ms</td></td><td>The maximum time in ms that a message in any topic is kept in memory before flushed to disk. If not set, the value in log.flush.scheduler.interval.ms is used</td></td><td>long</td></td><td>null</td></td><td></td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.flush.offset.checkpoint.interval.ms</td></td><td>The frequency with which we update the persistent record of the last flush which acts as the log recovery point</td></td><td>int</td></td><td>60000</td></td><td>[0,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>log.flush.scheduler.interval.ms</td></td><td>The frequency in ms that the log flusher checks whether any log needs to be flushed to disk</td></td><td>long</td></td><td>9223372036854775807</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>log.flush.start.offset.checkpoint.interval.ms</td></td><td>The frequency with which we update the persistent record of log start offset</td></td><td>int</td></td><td>60000</td></td><td>[0,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>log.retention.bytes</td></td><td>The maximum size of the log before deleting it</td></td><td>long</td></td><td>-1</td></td><td></td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.retention.hours</td></td><td>The number of hours to keep a log file before deleting it (in hours), tertiary to log.retention.ms property</td></td><td>int</td></td><td>168</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>log.retention.minutes</td></td><td>The number of minutes to keep a log file before deleting it (in minutes), secondary to log.retention.ms property. If not set, the value in log.retention.hours is used</td></td><td>int</td></td><td>null</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>log.retention.ms</td></td><td>The number of milliseconds to keep a log file before deleting it (in milliseconds), If not set, the value in log.retention.minutes is used</td></td><td>long</td></td><td>null</td></td><td></td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.roll.hours</td></td><td>The maximum time before a new log segment is rolled out (in hours), secondary to log.roll.ms property</td></td><td>int</td></td><td>168</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>log.roll.jitter.hours</td></td><td>The maximum jitter to subtract from logRollTimeMillis (in hours), secondary to log.roll.jitter.ms property</td></td><td>int</td></td><td>0</td></td><td>[0,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>log.roll.jitter.ms</td></td><td>The maximum jitter to subtract from logRollTimeMillis (in milliseconds). If not set, the value in log.roll.jitter.hours is used</td></td><td>long</td></td><td>null</td></td><td></td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.roll.ms</td></td><td>The maximum time before a new log segment is rolled out (in milliseconds). If not set, the value in log.roll.hours is used</td></td><td>long</td></td><td>null</td></td><td></td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.segment.bytes</td></td><td>The maximum size of a single log file</td></td><td>int</td></td><td>1073741824</td></td><td>[14,...]</td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.segment.delete.delay.ms</td></td><td>The amount of time to wait before deleting a file from the filesystem</td></td><td>long</td></td><td>60000</td></td><td>[0,...]</td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>message.max.bytes</td></td><td><p>The largest record batch size allowed by Kafka. If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that the they can fetch record batches this large.</p><p>In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in th [...]
+<tr>
+<td>min.insync.replicas</td></td><td>When a producer sets acks to "all" (or "-1"), min.insync.replicas specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend).<br>When used together, min.insync.replicas and acks allow you to enforce greater durability guarantees. A typical scenario would be to create  [...]
+<tr>
+<td>num.io.threads</td></td><td>The number of threads that the server uses for processing requests, which may include disk I/O</td></td><td>int</td></td><td>8</td></td><td>[1,...]</td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>num.network.threads</td></td><td>The number of threads that the server uses for receiving requests from the network and sending responses to the network</td></td><td>int</td></td><td>3</td></td><td>[1,...]</td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>num.recovery.threads.per.data.dir</td></td><td>The number of threads per data directory to be used for log recovery at startup and flushing at shutdown</td></td><td>int</td></td><td>1</td></td><td>[1,...]</td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>num.replica.alter.log.dirs.threads</td></td><td>The number of threads that can move replicas between log directories, which may include disk I/O</td></td><td>int</td></td><td>null</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>num.replica.fetchers</td></td><td>Number of fetcher threads used to replicate messages from a source broker. Increasing this value can increase the degree of I/O parallelism in the follower broker.</td></td><td>int</td></td><td>1</td></td><td></td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>offset.metadata.max.bytes</td></td><td>The maximum size for a metadata entry associated with an offset commit</td></td><td>int</td></td><td>4096</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>offsets.commit.required.acks</td></td><td>The required acks before the commit can be accepted. In general, the default (-1) should not be overridden</td></td><td>short</td></td><td>-1</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>offsets.commit.timeout.ms</td></td><td>Offset commit will be delayed until all replicas for the offsets topic receive the commit or this timeout is reached. This is similar to the producer request timeout.</td></td><td>int</td></td><td>5000</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>offsets.load.buffer.size</td></td><td>Batch size for reading from the offsets segments when loading offsets into the cache (soft-limit, overridden if records are too large).</td></td><td>int</td></td><td>5242880</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>offsets.retention.check.interval.ms</td></td><td>Frequency at which to check for stale offsets</td></td><td>long</td></td><td>600000</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>offsets.retention.minutes</td></td><td>After a consumer group loses all its consumers (i.e. becomes empty) its offsets will be kept for this retention period before getting discarded. For standalone consumers (using manual assignment), offsets will be expired after the time of last commit plus this retention period.</td></td><td>int</td></td><td>10080</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>offsets.topic.compression.codec</td></td><td>Compression codec for the offsets topic - compression may be used to achieve "atomic" commits</td></td><td>int</td></td><td>0</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>offsets.topic.num.partitions</td></td><td>The number of partitions for the offset commit topic (should not change after deployment)</td></td><td>int</td></td><td>50</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>offsets.topic.replication.factor</td></td><td>The replication factor for the offsets topic (set higher to ensure availability). Internal topic creation will fail until the cluster size meets this replication factor requirement.</td></td><td>short</td></td><td>3</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>offsets.topic.segment.bytes</td></td><td>The offsets topic segment bytes should be kept relatively small in order to facilitate faster log compaction and cache loads</td></td><td>int</td></td><td>104857600</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>port</td></td><td>DEPRECATED: only used when <code>listeners</code> is not set. Use <code>listeners</code> instead. 
+the port to listen and accept connections on</td></td><td>int</td></td><td>9092</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>queued.max.requests</td></td><td>The number of queued requests allowed before blocking the network threads</td></td><td>int</td></td><td>500</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>quota.consumer.default</td></td><td>DEPRECATED: Used only when dynamic default quotas are not configured for <user, <client-id> or <user, client-id> in Zookeeper. Any consumer distinguished by clientId/consumer group will get throttled if it fetches more bytes than this value per-second</td></td><td>long</td></td><td>9223372036854775807</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>quota.producer.default</td></td><td>DEPRECATED: Used only when dynamic default quotas are not configured for <user>, <client-id> or <user, client-id> in Zookeeper. Any producer distinguished by clientId will get throttled if it produces more bytes than this value per-second</td></td><td>long</td></td><td>9223372036854775807</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>replica.fetch.min.bytes</td></td><td>Minimum bytes expected for each fetch response. If not enough bytes, wait up to replicaMaxWaitTimeMs</td></td><td>int</td></td><td>1</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>replica.fetch.wait.max.ms</td></td><td>max wait time for each fetcher request issued by follower replicas. This value should always be less than the replica.lag.time.max.ms at all times to prevent frequent shrinking of ISR for low throughput topics</td></td><td>int</td></td><td>500</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>replica.high.watermark.checkpoint.interval.ms</td></td><td>The frequency with which the high watermark is saved out to disk</td></td><td>long</td></td><td>5000</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>replica.lag.time.max.ms</td></td><td>If a follower hasn't sent any fetch requests or hasn't consumed up to the leaders log end offset for at least this time, the leader will remove the follower from isr</td></td><td>long</td></td><td>10000</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>replica.socket.receive.buffer.bytes</td></td><td>The socket receive buffer for network requests</td></td><td>int</td></td><td>65536</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>replica.socket.timeout.ms</td></td><td>The socket timeout for network requests. Its value should be at least replica.fetch.wait.max.ms</td></td><td>int</td></td><td>30000</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>request.timeout.ms</td></td><td>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.</td></td><td>int</td></td><td>30000</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>socket.receive.buffer.bytes</td></td><td>The SO_RCVBUF buffer of the socket sever sockets. If the value is -1, the OS default will be used.</td></td><td>int</td></td><td>102400</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>socket.request.max.bytes</td></td><td>The maximum number of bytes in a socket request</td></td><td>int</td></td><td>104857600</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>socket.send.buffer.bytes</td></td><td>The SO_SNDBUF buffer of the socket sever sockets. If the value is -1, the OS default will be used.</td></td><td>int</td></td><td>102400</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>transaction.max.timeout.ms</td></td><td>The maximum allowed timeout for transactions. If a client’s requested transaction time exceed this, then the broker will return an error in InitProducerIdRequest. This prevents a client from too large of a timeout, which can stall consumers reading from topics included in the transaction.</td></td><td>int</td></td><td>900000</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>transaction.state.log.load.buffer.size</td></td><td>Batch size for reading from the transaction log segments when loading producer ids and transactions into the cache (soft-limit, overridden if records are too large).</td></td><td>int</td></td><td>5242880</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>transaction.state.log.min.isr</td></td><td>Overridden min.insync.replicas config for the transaction topic.</td></td><td>int</td></td><td>2</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>transaction.state.log.num.partitions</td></td><td>The number of partitions for the transaction topic (should not change after deployment).</td></td><td>int</td></td><td>50</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>transaction.state.log.replication.factor</td></td><td>The replication factor for the transaction topic (set higher to ensure availability). Internal topic creation will fail until the cluster size meets this replication factor requirement.</td></td><td>short</td></td><td>3</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>transaction.state.log.segment.bytes</td></td><td>The transaction topic segment bytes should be kept relatively small in order to facilitate faster log compaction and cache loads</td></td><td>int</td></td><td>104857600</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>transactional.id.expiration.ms</td></td><td>The maximum amount of time in ms that the transaction coordinator will wait before proactively expire a producer's transactional id without receiving any transaction status updates from it.</td></td><td>int</td></td><td>604800000</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>unclean.leader.election.enable</td></td><td>Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss</td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>high</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>zookeeper.connection.timeout.ms</td></td><td>The max time that the client waits to establish a connection to zookeeper. If not set, the value in zookeeper.session.timeout.ms is used</td></td><td>int</td></td><td>null</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>zookeeper.max.in.flight.requests</td></td><td>The maximum number of unacknowledged requests the client will send to Zookeeper before blocking.</td></td><td>int</td></td><td>10</td></td><td>[1,...]</td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>zookeeper.session.timeout.ms</td></td><td>Zookeeper session timeout</td></td><td>int</td></td><td>6000</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>zookeeper.set.acl</td></td><td>Set client to use secure ACLs</td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>high</td></td><td>read-only</td></tr>
+<tr>
+<td>broker.id.generation.enable</td></td><td>Enable automatic broker id generation on the server. When enabled the value configured for reserved.broker.max.id should be reviewed.</td></td><td>boolean</td></td><td>true</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>broker.rack</td></td><td>Rack of the broker. This will be used in rack aware replication assignment for fault tolerance. Examples: `RACK1`, `us-east-1d`</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>connections.max.idle.ms</td></td><td>Idle connections timeout: the server socket processor threads close the connections that idle more than this</td></td><td>long</td></td><td>600000</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>controlled.shutdown.enable</td></td><td>Enable controlled shutdown of the server</td></td><td>boolean</td></td><td>true</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>controlled.shutdown.max.retries</td></td><td>Controlled shutdown can fail for multiple reasons. This determines the number of retries when such failure happens</td></td><td>int</td></td><td>3</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>controlled.shutdown.retry.backoff.ms</td></td><td>Before each retry, the system needs time to recover from the state that caused the previous failure (Controller fail over, replica lag etc). This config determines the amount of time to wait before retrying.</td></td><td>long</td></td><td>5000</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>controller.socket.timeout.ms</td></td><td>The socket timeout for controller-to-broker channels</td></td><td>int</td></td><td>30000</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>default.replication.factor</td></td><td>default replication factors for automatically created topics</td></td><td>int</td></td><td>1</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>delegation.token.expiry.time.ms</td></td><td>The token validity time in miliseconds before the token needs to be renewed. Default value 1 day.</td></td><td>long</td></td><td>86400000</td></td><td>[1,...]</td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>delegation.token.master.key</td></td><td>Master/secret key to generate and verify delegation tokens. Same key must be configured across all the brokers.  If the key is not set or set to empty string, brokers will disable the delegation token support.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>delegation.token.max.lifetime.ms</td></td><td>The token has a maximum lifetime beyond which it cannot be renewed anymore. Default value 7 days.</td></td><td>long</td></td><td>604800000</td></td><td>[1,...]</td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>delete.records.purgatory.purge.interval.requests</td></td><td>The purge interval (in number of requests) of the delete records request purgatory</td></td><td>int</td></td><td>1</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>fetch.purgatory.purge.interval.requests</td></td><td>The purge interval (in number of requests) of the fetch request purgatory</td></td><td>int</td></td><td>1000</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>group.initial.rebalance.delay.ms</td></td><td>The amount of time the group coordinator will wait for more consumers to join a new group before performing the first rebalance. A longer delay means potentially fewer rebalances, but increases the time until processing begins.</td></td><td>int</td></td><td>3000</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>group.max.session.timeout.ms</td></td><td>The maximum allowed session timeout for registered consumers. Longer timeouts give consumers more time to process messages in between heartbeats at the cost of a longer time to detect failures.</td></td><td>int</td></td><td>300000</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>group.min.session.timeout.ms</td></td><td>The minimum allowed session timeout for registered consumers. Shorter timeouts result in quicker failure detection at the cost of more frequent consumer heartbeating, which can overwhelm broker resources.</td></td><td>int</td></td><td>6000</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>inter.broker.listener.name</td></td><td>Name of listener used for communication between brokers. If this is unset, the listener name is defined by security.inter.broker.protocol. It is an error to set this and security.inter.broker.protocol properties at the same time.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>inter.broker.protocol.version</td></td><td>Specify which version of the inter-broker protocol will be used.
+ This is typically bumped after all brokers were upgraded to a new version.
+ Example of some valid values are: 0.8.0, 0.8.1, 0.8.1.1, 0.8.2, 0.8.2.0, 0.8.2.1, 0.9.0.0, 0.9.0.1 Check ApiVersion for the full list.</td></td><td>string</td></td><td>2.1-IV2</td></td><td>kafka.api.ApiVersionValidator$@4eb7f003</td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>log.cleaner.backoff.ms</td></td><td>The amount of time to sleep when there are no logs to clean</td></td><td>long</td></td><td>15000</td></td><td>[0,...]</td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.cleaner.dedupe.buffer.size</td></td><td>The total memory used for log deduplication across all cleaner threads</td></td><td>long</td></td><td>134217728</td></td><td></td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.cleaner.delete.retention.ms</td></td><td>How long are delete records retained?</td></td><td>long</td></td><td>86400000</td></td><td></td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.cleaner.enable</td></td><td>Enable the log cleaner process to run on the server. Should be enabled if using any topics with a cleanup.policy=compact including the internal offsets topic. If disabled those topics will not be compacted and continually grow in size.</td></td><td>boolean</td></td><td>true</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>log.cleaner.io.buffer.load.factor</td></td><td>Log cleaner dedupe buffer load factor. The percentage full the dedupe buffer can become. A higher value will allow more log to be cleaned at once but will lead to more hash collisions</td></td><td>double</td></td><td>0.9</td></td><td></td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.cleaner.io.buffer.size</td></td><td>The total memory used for log cleaner I/O buffers across all cleaner threads</td></td><td>int</td></td><td>524288</td></td><td>[0,...]</td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.cleaner.io.max.bytes.per.second</td></td><td>The log cleaner will be throttled so that the sum of its read and write i/o will be less than this value on average</td></td><td>double</td></td><td>1.7976931348623157E308</td></td><td></td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.cleaner.min.cleanable.ratio</td></td><td>The minimum ratio of dirty log to total log for a log to eligible for cleaning</td></td><td>double</td></td><td>0.5</td></td><td></td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.cleaner.min.compaction.lag.ms</td></td><td>The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.</td></td><td>long</td></td><td>0</td></td><td></td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.cleaner.threads</td></td><td>The number of background threads to use for log cleaning</td></td><td>int</td></td><td>1</td></td><td>[0,...]</td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.cleanup.policy</td></td><td>The default cleanup policy for segments beyond the retention window. A comma separated list of valid policies. Valid policies are: "delete" and "compact"</td></td><td>list</td></td><td>delete</td></td><td>[compact, delete]</td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.index.interval.bytes</td></td><td>The interval with which we add an entry to the offset index</td></td><td>int</td></td><td>4096</td></td><td>[0,...]</td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.index.size.max.bytes</td></td><td>The maximum size in bytes of the offset index</td></td><td>int</td></td><td>10485760</td></td><td>[4,...]</td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.message.format.version</td></td><td>Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as  [...]
+<tr>
+<td>log.message.timestamp.difference.max.ms</td></td><td>The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If log.message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. This configuration is ignored if log.message.timestamp.type=LogAppendTime.The maximum timestamp difference allowed should be no greater than log.retention.ms to avoid unnecessarily  [...]
+<tr>
+<td>log.message.timestamp.type</td></td><td>Define whether the timestamp in the message is message create time or log append time. The value should be either `CreateTime` or `LogAppendTime`</td></td><td>string</td></td><td>CreateTime</td></td><td>[CreateTime, LogAppendTime]</td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.preallocate</td></td><td>Should pre allocate file when create new segment? If you are using Kafka on Windows, you probably need to set it to true.</td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>log.retention.check.interval.ms</td></td><td>The frequency in milliseconds that the log cleaner checks whether any log is eligible for deletion</td></td><td>long</td></td><td>300000</td></td><td>[1,...]</td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>max.connections.per.ip</td></td><td>The maximum number of connections we allow from each ip address. This can be set to 0 if there are overrides configured using max.connections.per.ip.overrides property</td></td><td>int</td></td><td>2147483647</td></td><td>[0,...]</td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>max.connections.per.ip.overrides</td></td><td>A comma-separated list of per-ip or hostname overrides to the default maximum number of connections. An example value is "hostName:100,127.0.0.1:200"</td></td><td>string</td></td><td>""</td></td><td></td></td><td>medium</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>max.incremental.fetch.session.cache.slots</td></td><td>The maximum number of incremental fetch sessions that we will maintain.</td></td><td>int</td></td><td>1000</td></td><td>[0,...]</td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>num.partitions</td></td><td>The default number of log partitions per topic</td></td><td>int</td></td><td>1</td></td><td>[1,...]</td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>password.encoder.old.secret</td></td><td>The old secret that was used for encoding dynamically configured passwords. This is required only when the secret is updated. If specified, all dynamically encoded passwords are decoded using this old secret and re-encoded using password.encoder.secret when broker starts up.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>password.encoder.secret</td></td><td>The secret used for encoding dynamically configured passwords for this broker.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>principal.builder.class</td></td><td>The fully qualified name of a class that implements the KafkaPrincipalBuilder interface, which is used to build the KafkaPrincipal object used during authorization. This config also supports the deprecated PrincipalBuilder interface which was previously used for client authentication over SSL. If no principal builder is defined, the default behavior depends on the security protocol in use. For SSL authentication, the principal name will be the dis [...]
+<tr>
+<td>producer.purgatory.purge.interval.requests</td></td><td>The purge interval (in number of requests) of the producer request purgatory</td></td><td>int</td></td><td>1000</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>queued.max.request.bytes</td></td><td>The number of queued bytes allowed before no more requests are read</td></td><td>long</td></td><td>-1</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>replica.fetch.backoff.ms</td></td><td>The amount of time to sleep when fetch partition error occurs.</td></td><td>int</td></td><td>1000</td></td><td>[0,...]</td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>replica.fetch.max.bytes</td></td><td>The number of bytes of messages to attempt to fetch for each partition. This is not an absolute maximum, if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that progress can be made. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker config) or <code>max.message.bytes</code> (topic config).</td>< [...]
+<tr>
+<td>replica.fetch.response.max.bytes</td></td><td>Maximum bytes expected for the entire fetch response. Records are fetched in batches, and if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that progress can be made. As such, this is not an absolute maximum. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker config) or <code>max.messag [...]
+<tr>
+<td>reserved.broker.max.id</td></td><td>Max number that can be used for a broker.id</td></td><td>int</td></td><td>1000</td></td><td>[0,...]</td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>sasl.client.callback.handler.class</td></td><td>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>sasl.enabled.mechanisms</td></td><td>The list of SASL mechanisms enabled in the Kafka server. The list may contain any mechanism for which a security provider is available. Only GSSAPI is enabled by default.</td></td><td>list</td></td><td>GSSAPI</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>sasl.jaas.config</td></td><td>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- [...]
+<tr>
+<td>sasl.kerberos.kinit.cmd</td></td><td>Kerberos kinit command path.</td></td><td>string</td></td><td>/usr/bin/kinit</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>sasl.kerberos.min.time.before.relogin</td></td><td>Login thread sleep time between refresh attempts.</td></td><td>long</td></td><td>60000</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>sasl.kerberos.principal.to.local.rules</td></td><td>A list of rules for mapping from principal names to short names (typically operating system usernames). The rules are evaluated in order and the first rule that matches a principal name is used to map it to a short name. Any later rules in the list are ignored. By default, principal names of the form {username}/{hostname}@{REALM} are mapped to {username}. For more details on the format please see <a href="#security_authz"> security  [...]
+<tr>
+<td>sasl.kerberos.service.name</td></td><td>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.jitter</td></td><td>Percentage of random jitter added to the renewal time.</td></td><td>double</td></td><td>0.05</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>sasl.login.callback.handler.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium [...]
+<tr>
+<td>sasl.login.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>sasl.login.refresh.buffer.seconds</td></td><td>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.pe [...]
+<tr>
+<td>sasl.login.refresh.min.period.seconds</td></td><td>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.</td></td><td>short</td></td><td>60</td></td><td [...]
+<tr>
+<td>sasl.login.refresh.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>sasl.login.refresh.window.jitter</td></td><td>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.</td></td><td>double</td></td><td>0.05</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>sasl.mechanism.inter.broker.protocol</td></td><td>SASL mechanism used for inter-broker communication. Default is GSSAPI.</td></td><td>string</td></td><td>GSSAPI</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>sasl.server.callback.handler.class</td></td><td>The fully qualified name of a SASL server callback handler class that implements the AuthenticateCallbackHandler interface. Server callback handlers must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.plain.sasl.server.callback.handler.class=com.example.CustomPlainCallbackHandler.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>security.inter.broker.protocol</td></td><td>Security protocol used to communicate between brokers. Valid values are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL. It is an error to set this and inter.broker.listener.name properties at the same time.</td></td><td>string</td></td><td>PLAINTEXT</td></td><td></td></td><td>medium</td></td><td>read-only</td></tr>
+<tr>
+<td>ssl.cipher.suites</td></td><td>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.</td></td><td>list</td></td><td>""</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.client.auth</td></td><td>Configures kafka broker to request client authentication. The following settings are common:  <ul> <li><code>ssl.client.auth=required</code> If set to required client authentication is required. <li><code>ssl.client.auth=requested</code> This means client authentication is optional. unlike requested , if this option is set client can choose not to provide authentication information about itself <li><code>ssl.client.auth=none</code> This means client authe [...]
+<tr>
+<td>ssl.enabled.protocols</td></td><td>The list of protocols enabled for SSL connections.</td></td><td>list</td></td><td>TLSv1.2,TLSv1.1,TLSv1</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.key.password</td></td><td>The password of the private key in the key store file. This is optional for client.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.keymanager.algorithm</td></td><td>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>SunX509</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.keystore.location</td></td><td>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.keystore.password</td></td><td>The store password for the key store file. This is optional for client and only needed if ssl.keystore.location is configured. </td></td><td>password</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.keystore.type</td></td><td>The file format of the key store file. This is optional for client.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.protocol</td></td><td>The SSL protocol used to generate the SSLContext. Default setting is TLS, which is fine for most cases. Allowed values in recent JVMs are TLS, TLSv1.1 and TLSv1.2. SSL, SSLv2 and SSLv3 may be supported in older JVMs, but their usage is discouraged due to known security vulnerabilities.</td></td><td>string</td></td><td>TLS</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.provider</td></td><td>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.trustmanager.algorithm</td></td><td>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>PKIX</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.truststore.location</td></td><td>The location of the trust store file. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.truststore.password</td></td><td>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.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.truststore.type</td></td><td>The file format of the trust store file.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td><td>per-broker</td></tr>
+<tr>
+<td>alter.config.policy.class.name</td></td><td>The alter configs policy class that should be used for validation. The class should implement the <code>org.apache.kafka.server.policy.AlterConfigPolicy</code> interface.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>alter.log.dirs.replication.quota.window.num</td></td><td>The number of samples to retain in memory for alter log dirs replication quotas</td></td><td>int</td></td><td>11</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>alter.log.dirs.replication.quota.window.size.seconds</td></td><td>The time span of each sample for alter log dirs replication quotas</td></td><td>int</td></td><td>1</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>authorizer.class.name</td></td><td>The authorizer class that should be used for authorization</td></td><td>string</td></td><td>""</td></td><td></td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>client.quota.callback.class</td></td><td>The fully qualified name of a class that implements the ClientQuotaCallback interface, which is used to determine quota limits applied to client requests. By default, <user, client-id>, <user> or <client-id> quotas stored in ZooKeeper are applied. For any given request, the most specific quota that matches the user principal of the session and the client-id of the request is applied.</td></td><td>class</td></td><td>null</td></td><td></td></td> [...]
+<tr>
+<td>connection.failed.authentication.delay.ms</td></td><td>Connection close delay on failed authentication: this is the time (in milliseconds) by which connection close will be delayed on authentication failure. This must be configured to be less than connections.max.idle.ms to prevent connection timeout.</td></td><td>int</td></td><td>100</td></td><td>[0,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>create.topic.policy.class.name</td></td><td>The create topic policy class that should be used for validation. The class should implement the <code>org.apache.kafka.server.policy.CreateTopicPolicy</code> interface.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>delegation.token.expiry.check.interval.ms</td></td><td>Scan interval to remove expired delegation tokens.</td></td><td>long</td></td><td>3600000</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>kafka.metrics.polling.interval.secs</td></td><td>The metrics polling interval (in seconds) which can be used in kafka.metrics.reporters implementations.</td></td><td>int</td></td><td>10</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>kafka.metrics.reporters</td></td><td>A list of classes to use as Yammer metrics custom reporters. The reporters should implement <code>kafka.metrics.KafkaMetricsReporter</code> trait. If a client wants to expose JMX operations on a custom reporter, the custom reporter needs to additionally implement an MBean trait that extends <code>kafka.metrics.KafkaMetricsReporterMBean</code> trait so that the registered MBean is compliant with the standard MBean convention.</td></td><td>list</td> [...]
+<tr>
+<td>listener.security.protocol.map</td></td><td>Map between listener names and security protocols. This must be defined for the same security protocol to be usable in more than one port or IP. For example, internal and external traffic can be separated even if SSL is required for both. Concretely, the user could define listeners with names INTERNAL and EXTERNAL and this property as: `INTERNAL:SSL,EXTERNAL:SSL`. As shown, key and value are separated by a colon and map entries are separate [...]
+<tr>
+<td>log.message.downconversion.enable</td></td><td>This configuration controls whether down-conversion of message formats is enabled to satisfy consume requests. When set to <code>false</code>, broker will not perform down-conversion for consumers expecting an older message format. The broker responds with <code>UNSUPPORTED_VERSION</code> error for consume requests from such older clients. This configurationdoes not apply to any message format conversion that might be required for replic [...]
+<tr>
+<td>metric.reporters</td></td><td>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.</td></td><td>list</td></td><td>""</td></td><td></td></td><td>low</td></td><td>cluster-wide</td></tr>
+<tr>
+<td>metrics.num.samples</td></td><td>The number of samples maintained to compute metrics.</td></td><td>int</td></td><td>2</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>metrics.recording.level</td></td><td>The highest recording level for metrics.</td></td><td>string</td></td><td>INFO</td></td><td></td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>metrics.sample.window.ms</td></td><td>The window of time a metrics sample is computed over.</td></td><td>long</td></td><td>30000</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>password.encoder.cipher.algorithm</td></td><td>The Cipher algorithm used for encoding dynamically configured passwords.</td></td><td>string</td></td><td>AES/CBC/PKCS5Padding</td></td><td></td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>password.encoder.iterations</td></td><td>The iteration count used for encoding dynamically configured passwords.</td></td><td>int</td></td><td>4096</td></td><td>[1024,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>password.encoder.key.length</td></td><td>The key length used for encoding dynamically configured passwords.</td></td><td>int</td></td><td>128</td></td><td>[8,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>password.encoder.keyfactory.algorithm</td></td><td>The SecretKeyFactory algorithm used for encoding dynamically configured passwords. Default is PBKDF2WithHmacSHA512 if available and PBKDF2WithHmacSHA1 otherwise.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>quota.window.num</td></td><td>The number of samples to retain in memory for client quotas</td></td><td>int</td></td><td>11</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>quota.window.size.seconds</td></td><td>The time span of each sample for client quotas</td></td><td>int</td></td><td>1</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>replication.quota.window.num</td></td><td>The number of samples to retain in memory for replication quotas</td></td><td>int</td></td><td>11</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>replication.quota.window.size.seconds</td></td><td>The time span of each sample for replication quotas</td></td><td>int</td></td><td>1</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>ssl.endpoint.identification.algorithm</td></td><td>The endpoint identification algorithm to validate server hostname using server certificate. </td></td><td>string</td></td><td>https</td></td><td></td></td><td>low</td></td><td>per-broker</td></tr>
+<tr>
+<td>ssl.secure.random.implementation</td></td><td>The SecureRandom PRNG implementation to use for SSL cryptography operations. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>low</td></td><td>per-broker</td></tr>
+<tr>
+<td>transaction.abort.timed.out.transaction.cleanup.interval.ms</td></td><td>The interval at which to rollback transactions that have timed out</td></td><td>int</td></td><td>60000</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>transaction.remove.expired.transaction.cleanup.interval.ms</td></td><td>The interval at which to remove transactions that have expired due to <code>transactional.id.expiration.ms<code> passing</td></td><td>int</td></td><td>3600000</td></td><td>[1,...]</td></td><td>low</td></td><td>read-only</td></tr>
+<tr>
+<td>zookeeper.sync.time.ms</td></td><td>How far a ZK follower can be behind a ZK leader</td></td><td>int</td></td><td>2000</td></td><td></td></td><td>low</td></td><td>read-only</td></tr>
+</tbody></table>
diff --git a/21/generated/producer_config.html b/21/generated/producer_config.html
index e69de29..79108e2 100644
--- a/21/generated/producer_config.html
+++ b/21/generated/producer_config.html
@@ -0,0 +1,134 @@
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>key.serializer</td></td><td>Serializer class for key that implements the <code>org.apache.kafka.common.serialization.Serializer</code> interface.</td></td><td>class</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>value.serializer</td></td><td>Serializer class for value that implements the <code>org.apache.kafka.common.serialization.Serializer</code> interface.</td></td><td>class</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>acks</td></td><td>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 th [...]
+<tr>
+<td>bootstrap.servers</td></td><td>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&mdash;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 me [...]
+<tr>
+<td>buffer.memory</td></td><td>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 [...]
+<tr>
+<td>compression.type</td></td><td>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).</td></td><td>string</td></td><td>none</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>retries</td></td><td>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 se [...]
+<tr>
+<td>ssl.key.password</td></td><td>The password of the private key in the key store file. This is optional for client.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.keystore.location</td></td><td>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.keystore.password</td></td><td>The store password for the key store file. This is optional for client and only needed if ssl.keystore.location is configured. </td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.truststore.location</td></td><td>The location of the trust store file. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>ssl.truststore.password</td></td><td>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.</td></td><td>password</td></td><td>null</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>batch.size</td></td><td>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 m [...]
+<tr>
+<td>client.dns.lookup</td></td><td><p>Controls how the client uses DNS lookups.</p><p>If set to <code>use_all_dns_ips</code> then, when the lookup returns multiple IP addresses for a hostname, they will all be attempted to connect to before failing the connection. Applies to both bootstrap and advertised servers.</p><p>If the value is <code>resolve_canonical_bootstrap_servers_only</code> each entry will be resolved and expanded into a list of canonical names.</p></td></td><td>string</td> [...]
+<tr>
+<td>client.id</td></td><td>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.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>connections.max.idle.ms</td></td><td>Close idle connections after the number of milliseconds specified by this config.</td></td><td>long</td></td><td>540000</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>delivery.timeout.ms</td></td><td>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 r [...]
+<tr>
+<td>linger.ms</td></td><td>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&mdash;that is, rather than immediately sending out a record the producer [...]
+<tr>
+<td>max.block.ms</td></td><td>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.</td></td><td>long</td></td><td>60000</td></td><td>[0,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>max.request.size</td></td><td>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 record batch size. Note that the server has its own cap on record batch size which may be different from this.</td></td><td>int</td></td><td>1048576</td></td><td>[0,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>partitioner.class</td></td><td>Partitioner class that implements the <code>org.apache.kafka.clients.producer.Partitioner</code> interface.</td></td><td>class</td></td><td>org.apache.kafka.clients.producer.internals.DefaultPartitioner</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>receive.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>32768</td></td><td>[-1,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>request.timeout.ms</td></td><td>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.</td></td><td>int</td>< [...]
+<tr>
+<td>sasl.client.callback.handler.class</td></td><td>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.jaas.config</td></td><td>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- [...]
+<tr>
+<td>sasl.kerberos.service.name</td></td><td>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.login.callback.handler.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium [...]
+<tr>
+<td>sasl.login.class</td></td><td>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</td></td><td>class</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>sasl.mechanism</td></td><td>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</td></td><td>string</td></td><td>GSSAPI</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>security.protocol</td></td><td>Protocol used to communicate with brokers. Valid values are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL.</td></td><td>string</td></td><td>PLAINTEXT</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>send.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>131072</td></td><td>[-1,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.enabled.protocols</td></td><td>The list of protocols enabled for SSL connections.</td></td><td>list</td></td><td>TLSv1.2,TLSv1.1,TLSv1</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.keystore.type</td></td><td>The file format of the key store file. This is optional for client.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.protocol</td></td><td>The SSL protocol used to generate the SSLContext. Default setting is TLS, which is fine for most cases. Allowed values in recent JVMs are TLS, TLSv1.1 and TLSv1.2. SSL, SSLv2 and SSLv3 may be supported in older JVMs, but their usage is discouraged due to known security vulnerabilities.</td></td><td>string</td></td><td>TLS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.provider</td></td><td>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</td></td><td>string</td></td><td>null</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>ssl.truststore.type</td></td><td>The file format of the trust store file.</td></td><td>string</td></td><td>JKS</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>enable.idempotence</td></td><td>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 expl [...]
+<tr>
+<td>interceptor.classes</td></td><td>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.</td></td><td>list</td></td><td>""</td></td><td>non-null string</td></td><td>low</td></td></tr>
+<tr>
+<td>max.in.flight.requests.per.connection</td></td><td>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).</td></td><td>int</td></td><td>5</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metadata.max.age.ms</td></td><td>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.</td></td><td>long</td></td><td>300000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metric.reporters</td></td><td>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.</td></td><td>list</td></td><td>""</td></td><td>non-null string</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.num.samples</td></td><td>The number of samples maintained to compute metrics.</td></td><td>int</td></td><td>2</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.recording.level</td></td><td>The highest recording level for metrics.</td></td><td>string</td></td><td>INFO</td></td><td>[INFO, DEBUG]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.sample.window.ms</td></td><td>The window of time a metrics sample is computed over.</td></td><td>long</td></td><td>30000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.max.ms</td></td><td>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.</td></td><td>long</td></td><td>1000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.ms</td></td><td>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.</td></td><td>long</td></td><td>50</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>retry.backoff.ms</td></td><td>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.</td></td><td>long</td></td><td>100</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.kinit.cmd</td></td><td>Kerberos kinit command path.</td></td><td>string</td></td><td>/usr/bin/kinit</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.min.time.before.relogin</td></td><td>Login thread sleep time between refresh attempts.</td></td><td>long</td></td><td>60000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.jitter</td></td><td>Percentage of random jitter added to the renewal time.</td></td><td>double</td></td><td>0.05</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.kerberos.ticket.renew.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.login.refresh.buffer.seconds</td></td><td>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.pe [...]
+<tr>
+<td>sasl.login.refresh.min.period.seconds</td></td><td>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.</td></td><td>short</td></td><td>60</td></td><td [...]
+<tr>
+<td>sasl.login.refresh.window.factor</td></td><td>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.</td></td><td>double</td></td><td>0.8</td></td><td>[0.5,...,1.0]</td></td><td>low</td></td></tr>
+<tr>
+<td>sasl.login.refresh.window.jitter</td></td><td>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.</td></td><td>double</td></td><td>0.05</td></td><td>[0.0,...,0.25]</td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.cipher.suites</td></td><td>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.</td></td><td>list</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.endpoint.identification.algorithm</td></td><td>The endpoint identification algorithm to validate server hostname using server certificate. </td></td><td>string</td></td><td>https</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.keymanager.algorithm</td></td><td>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>SunX509</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.secure.random.implementation</td></td><td>The SecureRandom PRNG implementation to use for SSL cryptography operations. </td></td><td>string</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>ssl.trustmanager.algorithm</td></td><td>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</td></td><td>string</td></td><td>PKIX</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>transaction.timeout.ms</td></td><td>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.</td></td><td>int</td></td><td>60000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>transactional.id</td></td><td>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. Note that <code>enable.idempotence</code> must be enabled if a TransactionalId is configured. [...]
+</tbody></table>
diff --git a/21/generated/producer_metrics.html b/21/generated/producer_metrics.html
index e69de29..deb4078 100644
--- a/21/generated/producer_metrics.html
+++ b/21/generated/producer_metrics.html
@@ -0,0 +1,78 @@
+<table class="data-table"><tbody>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.producer:type=producer-metrics,client-id="{client-id}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>batch-size-avg</td><td>The average number of bytes sent per partition per-request.</td></tr>
+<tr>
+<td></td><td>batch-size-max</td><td>The max number of bytes sent per partition per-request.</td></tr>
+<tr>
+<td></td><td>batch-split-rate</td><td>The average number of batch splits per second</td></tr>
+<tr>
+<td></td><td>batch-split-total</td><td>The total number of batch splits</td></tr>
+<tr>
+<td></td><td>compression-rate-avg</td><td>The average compression rate of record batches.</td></tr>
+<tr>
+<td></td><td>metadata-age</td><td>The age in seconds of the current producer metadata being used.</td></tr>
+<tr>
+<td></td><td>produce-throttle-time-avg</td><td>The average time in ms a request was throttled by a broker</td></tr>
+<tr>
+<td></td><td>produce-throttle-time-max</td><td>The maximum time in ms a request was throttled by a broker</td></tr>
+<tr>
+<td></td><td>record-error-rate</td><td>The average per-second number of record sends that resulted in errors</td></tr>
+<tr>
+<td></td><td>record-error-total</td><td>The total number of record sends that resulted in errors</td></tr>
+<tr>
+<td></td><td>record-queue-time-avg</td><td>The average time in ms record batches spent in the send buffer.</td></tr>
+<tr>
+<td></td><td>record-queue-time-max</td><td>The maximum time in ms record batches spent in the send buffer.</td></tr>
+<tr>
+<td></td><td>record-retry-rate</td><td>The average per-second number of retried record sends</td></tr>
+<tr>
+<td></td><td>record-retry-total</td><td>The total number of retried record sends</td></tr>
+<tr>
+<td></td><td>record-send-rate</td><td>The average number of records sent per second.</td></tr>
+<tr>
+<td></td><td>record-send-total</td><td>The total number of records sent.</td></tr>
+<tr>
+<td></td><td>record-size-avg</td><td>The average record size</td></tr>
+<tr>
+<td></td><td>record-size-max</td><td>The maximum record size</td></tr>
+<tr>
+<td></td><td>records-per-request-avg</td><td>The average number of records per request.</td></tr>
+<tr>
+<td></td><td>request-latency-avg</td><td>The average request latency in ms</td></tr>
+<tr>
+<td></td><td>request-latency-max</td><td>The maximum request latency in ms</td></tr>
+<tr>
+<td></td><td>requests-in-flight</td><td>The current number of in-flight requests awaiting a response.</td></tr>
+<tr>
+<td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.producer:type=producer-topic-metrics,client-id="{client-id}",topic="{topic}"</td></tr>
+<tr>
+<th style="width: 90px"></th>
+<th>Attribute name</th>
+<th>Description</th>
+</tr>
+<tr>
+<td></td><td>byte-rate</td><td>The average number of bytes sent per second for a topic.</td></tr>
+<tr>
+<td></td><td>byte-total</td><td>The total number of bytes sent for a topic.</td></tr>
+<tr>
+<td></td><td>compression-rate</td><td>The average compression rate of record batches for a topic.</td></tr>
+<tr>
+<td></td><td>record-error-rate</td><td>The average per-second number of record sends that resulted in errors for a topic</td></tr>
+<tr>
+<td></td><td>record-error-total</td><td>The total number of record sends that resulted in errors for a topic</td></tr>
+<tr>
+<td></td><td>record-retry-rate</td><td>The average per-second number of retried record sends for a topic</td></tr>
+<tr>
+<td></td><td>record-retry-total</td><td>The total number of retried record sends for a topic</td></tr>
+<tr>
+<td></td><td>record-send-rate</td><td>The average number of records sent per second for a topic.</td></tr>
+<tr>
+<td></td><td>record-send-total</td><td>The total number of records sent for a topic.</td></tr>
+</tbody></table>
diff --git a/21/generated/protocol_api_keys.html b/21/generated/protocol_api_keys.html
index e69de29..923716a 100644
--- a/21/generated/protocol_api_keys.html
+++ b/21/generated/protocol_api_keys.html
@@ -0,0 +1,91 @@
+<table class="data-table"><tbody>
+<tr><th>Name</th>
+<th>Key</th>
+</tr><tr>
+<td><a href="#The_Messages_Produce">Produce</a></td><td>0</td></tr>
+<tr>
+<td><a href="#The_Messages_Fetch">Fetch</a></td><td>1</td></tr>
+<tr>
+<td><a href="#The_Messages_ListOffsets">ListOffsets</a></td><td>2</td></tr>
+<tr>
+<td><a href="#The_Messages_Metadata">Metadata</a></td><td>3</td></tr>
+<tr>
+<td><a href="#The_Messages_LeaderAndIsr">LeaderAndIsr</a></td><td>4</td></tr>
+<tr>
+<td><a href="#The_Messages_StopReplica">StopReplica</a></td><td>5</td></tr>
+<tr>
+<td><a href="#The_Messages_UpdateMetadata">UpdateMetadata</a></td><td>6</td></tr>
+<tr>
+<td><a href="#The_Messages_ControlledShutdown">ControlledShutdown</a></td><td>7</td></tr>
+<tr>
+<td><a href="#The_Messages_OffsetCommit">OffsetCommit</a></td><td>8</td></tr>
+<tr>
+<td><a href="#The_Messages_OffsetFetch">OffsetFetch</a></td><td>9</td></tr>
+<tr>
+<td><a href="#The_Messages_FindCoordinator">FindCoordinator</a></td><td>10</td></tr>
+<tr>
+<td><a href="#The_Messages_JoinGroup">JoinGroup</a></td><td>11</td></tr>
+<tr>
+<td><a href="#The_Messages_Heartbeat">Heartbeat</a></td><td>12</td></tr>
+<tr>
+<td><a href="#The_Messages_LeaveGroup">LeaveGroup</a></td><td>13</td></tr>
+<tr>
+<td><a href="#The_Messages_SyncGroup">SyncGroup</a></td><td>14</td></tr>
+<tr>
+<td><a href="#The_Messages_DescribeGroups">DescribeGroups</a></td><td>15</td></tr>
+<tr>
+<td><a href="#The_Messages_ListGroups">ListGroups</a></td><td>16</td></tr>
+<tr>
+<td><a href="#The_Messages_SaslHandshake">SaslHandshake</a></td><td>17</td></tr>
+<tr>
+<td><a href="#The_Messages_ApiVersions">ApiVersions</a></td><td>18</td></tr>
+<tr>
+<td><a href="#The_Messages_CreateTopics">CreateTopics</a></td><td>19</td></tr>
+<tr>
+<td><a href="#The_Messages_DeleteTopics">DeleteTopics</a></td><td>20</td></tr>
+<tr>
+<td><a href="#The_Messages_DeleteRecords">DeleteRecords</a></td><td>21</td></tr>
+<tr>
+<td><a href="#The_Messages_InitProducerId">InitProducerId</a></td><td>22</td></tr>
+<tr>
+<td><a href="#The_Messages_OffsetForLeaderEpoch">OffsetForLeaderEpoch</a></td><td>23</td></tr>
+<tr>
+<td><a href="#The_Messages_AddPartitionsToTxn">AddPartitionsToTxn</a></td><td>24</td></tr>
+<tr>
+<td><a href="#The_Messages_AddOffsetsToTxn">AddOffsetsToTxn</a></td><td>25</td></tr>
+<tr>
+<td><a href="#The_Messages_EndTxn">EndTxn</a></td><td>26</td></tr>
+<tr>
+<td><a href="#The_Messages_WriteTxnMarkers">WriteTxnMarkers</a></td><td>27</td></tr>
+<tr>
+<td><a href="#The_Messages_TxnOffsetCommit">TxnOffsetCommit</a></td><td>28</td></tr>
+<tr>
+<td><a href="#The_Messages_DescribeAcls">DescribeAcls</a></td><td>29</td></tr>
+<tr>
+<td><a href="#The_Messages_CreateAcls">CreateAcls</a></td><td>30</td></tr>
+<tr>
+<td><a href="#The_Messages_DeleteAcls">DeleteAcls</a></td><td>31</td></tr>
+<tr>
+<td><a href="#The_Messages_DescribeConfigs">DescribeConfigs</a></td><td>32</td></tr>
+<tr>
+<td><a href="#The_Messages_AlterConfigs">AlterConfigs</a></td><td>33</td></tr>
+<tr>
+<td><a href="#The_Messages_AlterReplicaLogDirs">AlterReplicaLogDirs</a></td><td>34</td></tr>
+<tr>
+<td><a href="#The_Messages_DescribeLogDirs">DescribeLogDirs</a></td><td>35</td></tr>
+<tr>
+<td><a href="#The_Messages_SaslAuthenticate">SaslAuthenticate</a></td><td>36</td></tr>
+<tr>
+<td><a href="#The_Messages_CreatePartitions">CreatePartitions</a></td><td>37</td></tr>
+<tr>
+<td><a href="#The_Messages_CreateDelegationToken">CreateDelegationToken</a></td><td>38</td></tr>
+<tr>
+<td><a href="#The_Messages_RenewDelegationToken">RenewDelegationToken</a></td><td>39</td></tr>
+<tr>
+<td><a href="#The_Messages_ExpireDelegationToken">ExpireDelegationToken</a></td><td>40</td></tr>
+<tr>
+<td><a href="#The_Messages_DescribeDelegationToken">DescribeDelegationToken</a></td><td>41</td></tr>
+<tr>
+<td><a href="#The_Messages_DeleteGroups">DeleteGroups</a></td><td>42</td></tr>
+</table>
+
diff --git a/21/generated/protocol_errors.html b/21/generated/protocol_errors.html
index e69de29..a85c14b 100644
--- a/21/generated/protocol_errors.html
+++ b/21/generated/protocol_errors.html
@@ -0,0 +1,86 @@
+<table class="data-table"><tbody>
+<tr><th>Error</th>
+<th>Code</th>
+<th>Retriable</th>
+<th>Description</th>
+</tr>
+<tr><td>UNKNOWN_SERVER_ERROR</td><td>-1</td><td>False</td><td>The server experienced an unexpected error when processing the request.</td></tr>
+<tr><td>NONE</td><td>0</td><td>False</td><td></td></tr>
+<tr><td>OFFSET_OUT_OF_RANGE</td><td>1</td><td>False</td><td>The requested offset is not within the range of offsets maintained by the server.</td></tr>
+<tr><td>CORRUPT_MESSAGE</td><td>2</td><td>True</td><td>This message has failed its CRC checksum, exceeds the valid size, has a null key for a compacted topic, or is otherwise corrupt.</td></tr>
+<tr><td>UNKNOWN_TOPIC_OR_PARTITION</td><td>3</td><td>True</td><td>This server does not host this topic-partition.</td></tr>
+<tr><td>INVALID_FETCH_SIZE</td><td>4</td><td>False</td><td>The requested fetch size is invalid.</td></tr>
+<tr><td>LEADER_NOT_AVAILABLE</td><td>5</td><td>True</td><td>There is no leader for this topic-partition as we are in the middle of a leadership election.</td></tr>
+<tr><td>NOT_LEADER_FOR_PARTITION</td><td>6</td><td>True</td><td>This server is not the leader for that topic-partition.</td></tr>
+<tr><td>REQUEST_TIMED_OUT</td><td>7</td><td>True</td><td>The request timed out.</td></tr>
+<tr><td>BROKER_NOT_AVAILABLE</td><td>8</td><td>False</td><td>The broker is not available.</td></tr>
+<tr><td>REPLICA_NOT_AVAILABLE</td><td>9</td><td>False</td><td>The replica is not available for the requested topic-partition.</td></tr>
+<tr><td>MESSAGE_TOO_LARGE</td><td>10</td><td>False</td><td>The request included a message larger than the max message size the server will accept.</td></tr>
+<tr><td>STALE_CONTROLLER_EPOCH</td><td>11</td><td>False</td><td>The controller moved to another broker.</td></tr>
+<tr><td>OFFSET_METADATA_TOO_LARGE</td><td>12</td><td>False</td><td>The metadata field of the offset request was too large.</td></tr>
+<tr><td>NETWORK_EXCEPTION</td><td>13</td><td>True</td><td>The server disconnected before a response was received.</td></tr>
+<tr><td>COORDINATOR_LOAD_IN_PROGRESS</td><td>14</td><td>True</td><td>The coordinator is loading and hence can't process requests.</td></tr>
+<tr><td>COORDINATOR_NOT_AVAILABLE</td><td>15</td><td>True</td><td>The coordinator is not available.</td></tr>
+<tr><td>NOT_COORDINATOR</td><td>16</td><td>True</td><td>This is not the correct coordinator.</td></tr>
+<tr><td>INVALID_TOPIC_EXCEPTION</td><td>17</td><td>False</td><td>The request attempted to perform an operation on an invalid topic.</td></tr>
+<tr><td>RECORD_LIST_TOO_LARGE</td><td>18</td><td>False</td><td>The request included message batch larger than the configured segment size on the server.</td></tr>
+<tr><td>NOT_ENOUGH_REPLICAS</td><td>19</td><td>True</td><td>Messages are rejected since there are fewer in-sync replicas than required.</td></tr>
+<tr><td>NOT_ENOUGH_REPLICAS_AFTER_APPEND</td><td>20</td><td>True</td><td>Messages are written to the log, but to fewer in-sync replicas than required.</td></tr>
+<tr><td>INVALID_REQUIRED_ACKS</td><td>21</td><td>False</td><td>Produce request specified an invalid value for required acks.</td></tr>
+<tr><td>ILLEGAL_GENERATION</td><td>22</td><td>False</td><td>Specified group generation id is not valid.</td></tr>
+<tr><td>INCONSISTENT_GROUP_PROTOCOL</td><td>23</td><td>False</td><td>The group member's supported protocols are incompatible with those of existing members or first group member tried to join with empty protocol type or empty protocol list.</td></tr>
+<tr><td>INVALID_GROUP_ID</td><td>24</td><td>False</td><td>The configured groupId is invalid.</td></tr>
+<tr><td>UNKNOWN_MEMBER_ID</td><td>25</td><td>False</td><td>The coordinator is not aware of this member.</td></tr>
+<tr><td>INVALID_SESSION_TIMEOUT</td><td>26</td><td>False</td><td>The session timeout is not within the range allowed by the broker (as configured by group.min.session.timeout.ms and group.max.session.timeout.ms).</td></tr>
+<tr><td>REBALANCE_IN_PROGRESS</td><td>27</td><td>False</td><td>The group is rebalancing, so a rejoin is needed.</td></tr>
+<tr><td>INVALID_COMMIT_OFFSET_SIZE</td><td>28</td><td>False</td><td>The committing offset data size is not valid.</td></tr>
+<tr><td>TOPIC_AUTHORIZATION_FAILED</td><td>29</td><td>False</td><td>Not authorized to access topics: [Topic authorization failed.]</td></tr>
+<tr><td>GROUP_AUTHORIZATION_FAILED</td><td>30</td><td>False</td><td>Not authorized to access group: Group authorization failed.</td></tr>
+<tr><td>CLUSTER_AUTHORIZATION_FAILED</td><td>31</td><td>False</td><td>Cluster authorization failed.</td></tr>
+<tr><td>INVALID_TIMESTAMP</td><td>32</td><td>False</td><td>The timestamp of the message is out of acceptable range.</td></tr>
+<tr><td>UNSUPPORTED_SASL_MECHANISM</td><td>33</td><td>False</td><td>The broker does not support the requested SASL mechanism.</td></tr>
+<tr><td>ILLEGAL_SASL_STATE</td><td>34</td><td>False</td><td>Request is not valid given the current SASL state.</td></tr>
+<tr><td>UNSUPPORTED_VERSION</td><td>35</td><td>False</td><td>The version of API is not supported.</td></tr>
+<tr><td>TOPIC_ALREADY_EXISTS</td><td>36</td><td>False</td><td>Topic with this name already exists.</td></tr>
+<tr><td>INVALID_PARTITIONS</td><td>37</td><td>False</td><td>Number of partitions is below 1.</td></tr>
+<tr><td>INVALID_REPLICATION_FACTOR</td><td>38</td><td>False</td><td>Replication factor is below 1 or larger than the number of available brokers.</td></tr>
+<tr><td>INVALID_REPLICA_ASSIGNMENT</td><td>39</td><td>False</td><td>Replica assignment is invalid.</td></tr>
+<tr><td>INVALID_CONFIG</td><td>40</td><td>False</td><td>Configuration is invalid.</td></tr>
+<tr><td>NOT_CONTROLLER</td><td>41</td><td>True</td><td>This is not the correct controller for this cluster.</td></tr>
+<tr><td>INVALID_REQUEST</td><td>42</td><td>False</td><td>This most likely occurs because of a request being malformed by the client library or the message was sent to an incompatible broker. See the broker logs for more details.</td></tr>
+<tr><td>UNSUPPORTED_FOR_MESSAGE_FORMAT</td><td>43</td><td>False</td><td>The message format version on the broker does not support the request.</td></tr>
+<tr><td>POLICY_VIOLATION</td><td>44</td><td>False</td><td>Request parameters do not satisfy the configured policy.</td></tr>
+<tr><td>OUT_OF_ORDER_SEQUENCE_NUMBER</td><td>45</td><td>False</td><td>The broker received an out of order sequence number.</td></tr>
+<tr><td>DUPLICATE_SEQUENCE_NUMBER</td><td>46</td><td>False</td><td>The broker received a duplicate sequence number.</td></tr>
+<tr><td>INVALID_PRODUCER_EPOCH</td><td>47</td><td>False</td><td>Producer attempted an operation with an old epoch. Either there is a newer producer with the same transactionalId, or the producer's transaction has been expired by the broker.</td></tr>
+<tr><td>INVALID_TXN_STATE</td><td>48</td><td>False</td><td>The producer attempted a transactional operation in an invalid state.</td></tr>
+<tr><td>INVALID_PRODUCER_ID_MAPPING</td><td>49</td><td>False</td><td>The producer attempted to use a producer id which is not currently assigned to its transactional id.</td></tr>
+<tr><td>INVALID_TRANSACTION_TIMEOUT</td><td>50</td><td>False</td><td>The transaction timeout is larger than the maximum value allowed by the broker (as configured by transaction.max.timeout.ms).</td></tr>
+<tr><td>CONCURRENT_TRANSACTIONS</td><td>51</td><td>False</td><td>The producer attempted to update a transaction while another concurrent operation on the same transaction was ongoing.</td></tr>
+<tr><td>TRANSACTION_COORDINATOR_FENCED</td><td>52</td><td>False</td><td>Indicates that the transaction coordinator sending a WriteTxnMarker is no longer the current coordinator for a given producer.</td></tr>
+<tr><td>TRANSACTIONAL_ID_AUTHORIZATION_FAILED</td><td>53</td><td>False</td><td>Transactional Id authorization failed.</td></tr>
+<tr><td>SECURITY_DISABLED</td><td>54</td><td>False</td><td>Security features are disabled.</td></tr>
+<tr><td>OPERATION_NOT_ATTEMPTED</td><td>55</td><td>False</td><td>The broker did not attempt to execute this operation. This may happen for batched RPCs where some operations in the batch failed, causing the broker to respond without trying the rest.</td></tr>
+<tr><td>KAFKA_STORAGE_ERROR</td><td>56</td><td>True</td><td>Disk error when trying to access log file on the disk.</td></tr>
+<tr><td>LOG_DIR_NOT_FOUND</td><td>57</td><td>False</td><td>The user-specified log directory is not found in the broker config.</td></tr>
+<tr><td>SASL_AUTHENTICATION_FAILED</td><td>58</td><td>False</td><td>SASL Authentication failed.</td></tr>
+<tr><td>UNKNOWN_PRODUCER_ID</td><td>59</td><td>False</td><td>This exception is raised by the broker if it could not locate the producer metadata associated with the producerId in question. This could happen if, for instance, the producer's records were deleted because their retention time had elapsed. Once the last records of the producerId are removed, the producer's metadata is removed from the broker, and future appends by the producer will return this exception.</td></tr>
+<tr><td>REASSIGNMENT_IN_PROGRESS</td><td>60</td><td>False</td><td>A partition reassignment is in progress.</td></tr>
+<tr><td>DELEGATION_TOKEN_AUTH_DISABLED</td><td>61</td><td>False</td><td>Delegation Token feature is not enabled.</td></tr>
+<tr><td>DELEGATION_TOKEN_NOT_FOUND</td><td>62</td><td>False</td><td>Delegation Token is not found on server.</td></tr>
+<tr><td>DELEGATION_TOKEN_OWNER_MISMATCH</td><td>63</td><td>False</td><td>Specified Principal is not valid Owner/Renewer.</td></tr>
+<tr><td>DELEGATION_TOKEN_REQUEST_NOT_ALLOWED</td><td>64</td><td>False</td><td>Delegation Token requests are not allowed on PLAINTEXT/1-way SSL channels and on delegation token authenticated channels.</td></tr>
+<tr><td>DELEGATION_TOKEN_AUTHORIZATION_FAILED</td><td>65</td><td>False</td><td>Delegation Token authorization failed.</td></tr>
+<tr><td>DELEGATION_TOKEN_EXPIRED</td><td>66</td><td>False</td><td>Delegation Token is expired.</td></tr>
+<tr><td>INVALID_PRINCIPAL_TYPE</td><td>67</td><td>False</td><td>Supplied principalType is not supported.</td></tr>
+<tr><td>NON_EMPTY_GROUP</td><td>68</td><td>False</td><td>The group is not empty.</td></tr>
+<tr><td>GROUP_ID_NOT_FOUND</td><td>69</td><td>False</td><td>The group id does not exist.</td></tr>
+<tr><td>FETCH_SESSION_ID_NOT_FOUND</td><td>70</td><td>True</td><td>The fetch session ID was not found.</td></tr>
+<tr><td>INVALID_FETCH_SESSION_EPOCH</td><td>71</td><td>True</td><td>The fetch session epoch is invalid.</td></tr>
+<tr><td>LISTENER_NOT_FOUND</td><td>72</td><td>True</td><td>There is no listener on the leader broker that matches the listener on which metadata request was processed.</td></tr>
+<tr><td>TOPIC_DELETION_DISABLED</td><td>73</td><td>False</td><td>Topic deletion is disabled.</td></tr>
+<tr><td>FENCED_LEADER_EPOCH</td><td>74</td><td>True</td><td>The leader epoch in the request is older than the epoch on the broker</td></tr>
+<tr><td>UNKNOWN_LEADER_EPOCH</td><td>75</td><td>True</td><td>The leader epoch in the request is newer than the epoch on the broker</td></tr>
+<tr><td>UNSUPPORTED_COMPRESSION_TYPE</td><td>76</td><td>False</td><td>The requesting client does not support the compression type of given partition.</td></tr>
+</table>
+
diff --git a/21/generated/protocol_messages.html b/21/generated/protocol_messages.html
index e69de29..17a16d0 100644
--- a/21/generated/protocol_messages.html
+++ b/21/generated/protocol_messages.html
@@ -0,0 +1,7281 @@
+<h5>Headers:</h5>
+<pre>Request Header => api_key api_version correlation_id client_id 
+  api_key => INT16
+  api_version => INT16
+  correlation_id => INT32
+  client_id => NULLABLE_STRING
+</pre>
+<table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>api_key</td><td>The id of the request type.</td></tr>
+<tr>
+<td>api_version</td><td>The version of the API.</td></tr>
+<tr>
+<td>correlation_id</td><td>A user-supplied integer value that will be passed back with the response</td></tr>
+<tr>
+<td>client_id</td><td>A user specified identifier for the client making the request.</td></tr>
+</table>
+<pre>Response Header => correlation_id 
+  correlation_id => INT32
+</pre>
+<table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>correlation_id</td><td>The user-supplied value passed in with the request</td></tr>
+</table>
+<h5><a name="The_Messages_Produce">Produce API (Key: 0):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>Produce Request (Version: 0) => acks timeout [topic_data] 
+  acks => INT16
+  timeout => INT32
+  topic_data => topic [data] 
+    topic => STRING
+    data => partition record_set 
+      partition => INT32
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>acks</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. Allowed values: 0 for no acknowledgments, 1 for only the leader and -1 for the full ISR.</td></tr>
+<tr>
+<td>timeout</td><td>The time to await a response in ms.</td></tr>
+<tr>
+<td>topic_data</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>data</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Produce Request (Version: 1) => acks timeout [topic_data] 
+  acks => INT16
+  timeout => INT32
+  topic_data => topic [data] 
+    topic => STRING
+    data => partition record_set 
+      partition => INT32
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>acks</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. Allowed values: 0 for no acknowledgments, 1 for only the leader and -1 for the full ISR.</td></tr>
+<tr>
+<td>timeout</td><td>The time to await a response in ms.</td></tr>
+<tr>
+<td>topic_data</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>data</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Produce Request (Version: 2) => acks timeout [topic_data] 
+  acks => INT16
+  timeout => INT32
+  topic_data => topic [data] 
+    topic => STRING
+    data => partition record_set 
+      partition => INT32
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>acks</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. Allowed values: 0 for no acknowledgments, 1 for only the leader and -1 for the full ISR.</td></tr>
+<tr>
+<td>timeout</td><td>The time to await a response in ms.</td></tr>
+<tr>
+<td>topic_data</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>data</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Produce Request (Version: 3) => transactional_id acks timeout [topic_data] 
+  transactional_id => NULLABLE_STRING
+  acks => INT16
+  timeout => INT32
+  topic_data => topic [data] 
+    topic => STRING
+    data => partition record_set 
+      partition => INT32
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id or null if the producer is not transactional</td></tr>
+<tr>
+<td>acks</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. Allowed values: 0 for no acknowledgments, 1 for only the leader and -1 for the full ISR.</td></tr>
+<tr>
+<td>timeout</td><td>The time to await a response in ms.</td></tr>
+<tr>
+<td>topic_data</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>data</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Produce Request (Version: 4) => transactional_id acks timeout [topic_data] 
+  transactional_id => NULLABLE_STRING
+  acks => INT16
+  timeout => INT32
+  topic_data => topic [data] 
+    topic => STRING
+    data => partition record_set 
+      partition => INT32
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id or null if the producer is not transactional</td></tr>
+<tr>
+<td>acks</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. Allowed values: 0 for no acknowledgments, 1 for only the leader and -1 for the full ISR.</td></tr>
+<tr>
+<td>timeout</td><td>The time to await a response in ms.</td></tr>
+<tr>
+<td>topic_data</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>data</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Produce Request (Version: 5) => transactional_id acks timeout [topic_data] 
+  transactional_id => NULLABLE_STRING
+  acks => INT16
+  timeout => INT32
+  topic_data => topic [data] 
+    topic => STRING
+    data => partition record_set 
+      partition => INT32
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id or null if the producer is not transactional</td></tr>
+<tr>
+<td>acks</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. Allowed values: 0 for no acknowledgments, 1 for only the leader and -1 for the full ISR.</td></tr>
+<tr>
+<td>timeout</td><td>The time to await a response in ms.</td></tr>
+<tr>
+<td>topic_data</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>data</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Produce Request (Version: 6) => transactional_id acks timeout [topic_data] 
+  transactional_id => NULLABLE_STRING
+  acks => INT16
+  timeout => INT32
+  topic_data => topic [data] 
+    topic => STRING
+    data => partition record_set 
+      partition => INT32
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id or null if the producer is not transactional</td></tr>
+<tr>
+<td>acks</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. Allowed values: 0 for no acknowledgments, 1 for only the leader and -1 for the full ISR.</td></tr>
+<tr>
+<td>timeout</td><td>The time to await a response in ms.</td></tr>
+<tr>
+<td>topic_data</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>data</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Produce Request (Version: 7) => transactional_id acks timeout [topic_data] 
+  transactional_id => NULLABLE_STRING
+  acks => INT16
+  timeout => INT32
+  topic_data => topic [data] 
+    topic => STRING
+    data => partition record_set 
+      partition => INT32
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id or null if the producer is not transactional</td></tr>
+<tr>
+<td>acks</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. Allowed values: 0 for no acknowledgments, 1 for only the leader and -1 for the full ISR.</td></tr>
+<tr>
+<td>timeout</td><td>The time to await a response in ms.</td></tr>
+<tr>
+<td>topic_data</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>data</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>Produce Response (Version: 0) => [responses] 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code base_offset 
+      partition => INT32
+      error_code => INT16
+      base_offset => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>base_offset</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Produce Response (Version: 1) => [responses] throttle_time_ms 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code base_offset 
+      partition => INT32
+      error_code => INT16
+      base_offset => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>base_offset</td><td>null</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>Produce Response (Version: 2) => [responses] throttle_time_ms 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code base_offset log_append_time 
+      partition => INT32
+      error_code => INT16
+      base_offset => INT64
+      log_append_time => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>base_offset</td><td>null</td></tr>
+<tr>
+<td>log_append_time</td><td>The timestamp returned by broker after appending the messages. If CreateTime is used for the topic, the timestamp will be -1. If LogAppendTime is used for the topic, the timestamp will be the broker local time when the messages are appended.</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>Produce Response (Version: 3) => [responses] throttle_time_ms 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code base_offset log_append_time 
+      partition => INT32
+      error_code => INT16
+      base_offset => INT64
+      log_append_time => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>base_offset</td><td>null</td></tr>
+<tr>
+<td>log_append_time</td><td>The timestamp returned by broker after appending the messages. If CreateTime is used for the topic, the timestamp will be -1. If LogAppendTime is used for the topic, the timestamp will be the broker local time when the messages are appended.</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>Produce Response (Version: 4) => [responses] throttle_time_ms 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code base_offset log_append_time 
+      partition => INT32
+      error_code => INT16
+      base_offset => INT64
+      log_append_time => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>base_offset</td><td>null</td></tr>
+<tr>
+<td>log_append_time</td><td>The timestamp returned by broker after appending the messages. If CreateTime is used for the topic, the timestamp will be -1. If LogAppendTime is used for the topic, the timestamp will be the broker local time when the messages are appended.</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>Produce Response (Version: 5) => [responses] throttle_time_ms 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code base_offset log_append_time log_start_offset 
+      partition => INT32
+      error_code => INT16
+      base_offset => INT64
+      log_append_time => INT64
+      log_start_offset => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>base_offset</td><td>null</td></tr>
+<tr>
+<td>log_append_time</td><td>The timestamp returned by broker after appending the messages. If CreateTime is used for the topic, the timestamp will be -1. If LogAppendTime is used for the topic, the timestamp will be the broker local time when the messages are appended.</td></tr>
+<tr>
+<td>log_start_offset</td><td>The start offset of the log at the time this produce response was created</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>Produce Response (Version: 6) => [responses] throttle_time_ms 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code base_offset log_append_time log_start_offset 
+      partition => INT32
+      error_code => INT16
+      base_offset => INT64
+      log_append_time => INT64
+      log_start_offset => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>base_offset</td><td>null</td></tr>
+<tr>
+<td>log_append_time</td><td>The timestamp returned by broker after appending the messages. If CreateTime is used for the topic, the timestamp will be -1. If LogAppendTime is used for the topic, the timestamp will be the broker local time when the messages are appended.</td></tr>
+<tr>
+<td>log_start_offset</td><td>The start offset of the log at the time this produce response was created</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>Produce Response (Version: 7) => [responses] throttle_time_ms 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code base_offset log_append_time log_start_offset 
+      partition => INT32
+      error_code => INT16
+      base_offset => INT64
+      log_append_time => INT64
+      log_start_offset => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>base_offset</td><td>null</td></tr>
+<tr>
+<td>log_append_time</td><td>The timestamp returned by broker after appending the messages. If CreateTime is used for the topic, the timestamp will be -1. If LogAppendTime is used for the topic, the timestamp will be the broker local time when the messages are appended.</td></tr>
+<tr>
+<td>log_start_offset</td><td>The start offset of the log at the time this produce response was created</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_Fetch">Fetch API (Key: 1):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>Fetch Request (Version: 0) => replica_id max_wait_time min_bytes [topics] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition fetch_offset partition_max_bytes 
+      partition => INT32
+      fetch_offset => INT64
+      partition_max_bytes => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 1) => replica_id max_wait_time min_bytes [topics] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition fetch_offset partition_max_bytes 
+      partition => INT32
+      fetch_offset => INT64
+      partition_max_bytes => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 2) => replica_id max_wait_time min_bytes [topics] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition fetch_offset partition_max_bytes 
+      partition => INT32
+      fetch_offset => INT64
+      partition_max_bytes => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 3) => replica_id max_wait_time min_bytes max_bytes [topics] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  max_bytes => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition fetch_offset partition_max_bytes 
+      partition => INT32
+      fetch_offset => INT64
+      partition_max_bytes => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>max_bytes</td><td>Maximum bytes to accumulate in the response. Note that this is not an absolute maximum, if the first message in the first non-empty partition of the fetch is larger than this value, the message will still be returned to ensure that progress can be made.</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 4) => replica_id max_wait_time min_bytes max_bytes isolation_level [topics] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  max_bytes => INT32
+  isolation_level => INT8
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition fetch_offset partition_max_bytes 
+      partition => INT32
+      fetch_offset => INT64
+      partition_max_bytes => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>max_bytes</td><td>Maximum bytes to accumulate in the response. Note that this is not an absolute maximum, if the first message in the first non-empty partition of the fetch is larger than this value, the message will still be returned to ensure that progress can be made.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 5) => replica_id max_wait_time min_bytes max_bytes isolation_level [topics] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  max_bytes => INT32
+  isolation_level => INT8
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition fetch_offset log_start_offset partition_max_bytes 
+      partition => INT32
+      fetch_offset => INT64
+      log_start_offset => INT64
+      partition_max_bytes => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>max_bytes</td><td>Maximum bytes to accumulate in the response. Note that this is not an absolute maximum, if the first message in the first non-empty partition of the fetch is larger than this value, the message will still be returned to ensure that progress can be made.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset of the follower replica. The field is only used when request is sent by follower. </td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 6) => replica_id max_wait_time min_bytes max_bytes isolation_level [topics] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  max_bytes => INT32
+  isolation_level => INT8
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition fetch_offset log_start_offset partition_max_bytes 
+      partition => INT32
+      fetch_offset => INT64
+      log_start_offset => INT64
+      partition_max_bytes => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>max_bytes</td><td>Maximum bytes to accumulate in the response. Note that this is not an absolute maximum, if the first message in the first non-empty partition of the fetch is larger than this value, the message will still be returned to ensure that progress can be made.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset of the follower replica. The field is only used when request is sent by follower. </td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 7) => replica_id max_wait_time min_bytes max_bytes isolation_level session_id session_epoch [topics] [forgotten_topics_data] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  max_bytes => INT32
+  isolation_level => INT8
+  session_id => INT32
+  session_epoch => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition fetch_offset log_start_offset partition_max_bytes 
+      partition => INT32
+      fetch_offset => INT64
+      log_start_offset => INT64
+      partition_max_bytes => INT32
+  forgotten_topics_data => topic [partitions] 
+    topic => STRING
+    partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>max_bytes</td><td>Maximum bytes to accumulate in the response. Note that this is not an absolute maximum, if the first message in the first non-empty partition of the fetch is larger than this value, the message will still be returned to ensure that progress can be made.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>session_id</td><td>The fetch session ID</td></tr>
+<tr>
+<td>session_epoch</td><td>The fetch session epoch</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset of the follower replica. The field is only used when request is sent by follower. </td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+<tr>
+<td>forgotten_topics_data</td><td>Topics to remove from the fetch session.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to remove from the fetch session.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 8) => replica_id max_wait_time min_bytes max_bytes isolation_level session_id session_epoch [topics] [forgotten_topics_data] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  max_bytes => INT32
+  isolation_level => INT8
+  session_id => INT32
+  session_epoch => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition fetch_offset log_start_offset partition_max_bytes 
+      partition => INT32
+      fetch_offset => INT64
+      log_start_offset => INT64
+      partition_max_bytes => INT32
+  forgotten_topics_data => topic [partitions] 
+    topic => STRING
+    partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>max_bytes</td><td>Maximum bytes to accumulate in the response. Note that this is not an absolute maximum, if the first message in the first non-empty partition of the fetch is larger than this value, the message will still be returned to ensure that progress can be made.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>session_id</td><td>The fetch session ID</td></tr>
+<tr>
+<td>session_epoch</td><td>The fetch session epoch</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset of the follower replica. The field is only used when request is sent by follower. </td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+<tr>
+<td>forgotten_topics_data</td><td>Topics to remove from the fetch session.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to remove from the fetch session.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 9) => replica_id max_wait_time min_bytes max_bytes isolation_level session_id session_epoch [topics] [forgotten_topics_data] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  max_bytes => INT32
+  isolation_level => INT8
+  session_id => INT32
+  session_epoch => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition current_leader_epoch fetch_offset log_start_offset partition_max_bytes 
+      partition => INT32
+      current_leader_epoch => INT32
+      fetch_offset => INT64
+      log_start_offset => INT64
+      partition_max_bytes => INT32
+  forgotten_topics_data => topic [partitions] 
+    topic => STRING
+    partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>max_bytes</td><td>Maximum bytes to accumulate in the response. Note that this is not an absolute maximum, if the first message in the first non-empty partition of the fetch is larger than this value, the message will still be returned to ensure that progress can be made.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>session_id</td><td>The fetch session ID</td></tr>
+<tr>
+<td>session_epoch</td><td>The fetch session epoch</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>current_leader_epoch</td><td>The current leader epoch, if provided, is used to fence consumers/replicas with old metadata. If the epoch provided by the client is larger than the current epoch known to the broker, then the UNKNOWN_LEADER_EPOCH error code will be returned. If the provided epoch is smaller, then the FENCED_LEADER_EPOCH error code will be returned.</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset of the follower replica. The field is only used when request is sent by follower. </td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+<tr>
+<td>forgotten_topics_data</td><td>Topics to remove from the fetch session.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to remove from the fetch session.</td></tr>
+</table>
+</p>
+<p><pre>Fetch Request (Version: 10) => replica_id max_wait_time min_bytes max_bytes isolation_level session_id session_epoch [topics] [forgotten_topics_data] 
+  replica_id => INT32
+  max_wait_time => INT32
+  min_bytes => INT32
+  max_bytes => INT32
+  isolation_level => INT8
+  session_id => INT32
+  session_epoch => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition current_leader_epoch fetch_offset log_start_offset partition_max_bytes 
+      partition => INT32
+      current_leader_epoch => INT32
+      fetch_offset => INT64
+      log_start_offset => INT64
+      partition_max_bytes => INT32
+  forgotten_topics_data => topic [partitions] 
+    topic => STRING
+    partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>max_wait_time</td><td>Maximum time in ms to wait for the response.</td></tr>
+<tr>
+<td>min_bytes</td><td>Minimum bytes to accumulate in the response.</td></tr>
+<tr>
+<td>max_bytes</td><td>Maximum bytes to accumulate in the response. Note that this is not an absolute maximum, if the first message in the first non-empty partition of the fetch is larger than this value, the message will still be returned to ensure that progress can be made.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>session_id</td><td>The fetch session ID</td></tr>
+<tr>
+<td>session_epoch</td><td>The fetch session epoch</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch in the order provided.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>current_leader_epoch</td><td>The current leader epoch, if provided, is used to fence consumers/replicas with old metadata. If the epoch provided by the client is larger than the current epoch known to the broker, then the UNKNOWN_LEADER_EPOCH error code will be returned. If the provided epoch is smaller, then the FENCED_LEADER_EPOCH error code will be returned.</td></tr>
+<tr>
+<td>fetch_offset</td><td>Message offset.</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset of the follower replica. The field is only used when request is sent by follower. </td></tr>
+<tr>
+<td>partition_max_bytes</td><td>Maximum bytes to fetch.</td></tr>
+<tr>
+<td>forgotten_topics_data</td><td>Topics to remove from the fetch session.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to remove from the fetch session.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>Fetch Response (Version: 0) => [responses] 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 1) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 2) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 3) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 4) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark last_stable_offset [aborted_transactions] 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+        last_stable_offset => INT64
+        aborted_transactions => producer_id first_offset 
+          producer_id => INT64
+          first_offset => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>last_stable_offset</td><td>The last stable offset (or LSO) of the partition. This is the last offset such that the state of all transactional records prior to this offset have been decided (ABORTED or COMMITTED)</td></tr>
+<tr>
+<td>aborted_transactions</td><td>null</td></tr>
+<tr>
+<td>producer_id</td><td>The producer id associated with the aborted transactions</td></tr>
+<tr>
+<td>first_offset</td><td>The first offset in the aborted transaction</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 5) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark last_stable_offset log_start_offset [aborted_transactions] 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+        last_stable_offset => INT64
+        log_start_offset => INT64
+        aborted_transactions => producer_id first_offset 
+          producer_id => INT64
+          first_offset => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>last_stable_offset</td><td>The last stable offset (or LSO) of the partition. This is the last offset such that the state of all transactional records prior to this offset have been decided (ABORTED or COMMITTED)</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset.</td></tr>
+<tr>
+<td>aborted_transactions</td><td>null</td></tr>
+<tr>
+<td>producer_id</td><td>The producer id associated with the aborted transactions</td></tr>
+<tr>
+<td>first_offset</td><td>The first offset in the aborted transaction</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 6) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark last_stable_offset log_start_offset [aborted_transactions] 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+        last_stable_offset => INT64
+        log_start_offset => INT64
+        aborted_transactions => producer_id first_offset 
+          producer_id => INT64
+          first_offset => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>last_stable_offset</td><td>The last stable offset (or LSO) of the partition. This is the last offset such that the state of all transactional records prior to this offset have been decided (ABORTED or COMMITTED)</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset.</td></tr>
+<tr>
+<td>aborted_transactions</td><td>null</td></tr>
+<tr>
+<td>producer_id</td><td>The producer id associated with the aborted transactions</td></tr>
+<tr>
+<td>first_offset</td><td>The first offset in the aborted transaction</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 7) => throttle_time_ms error_code session_id [responses] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  session_id => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark last_stable_offset log_start_offset [aborted_transactions] 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+        last_stable_offset => INT64
+        log_start_offset => INT64
+        aborted_transactions => producer_id first_offset 
+          producer_id => INT64
+          first_offset => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>session_id</td><td>The fetch session ID</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>last_stable_offset</td><td>The last stable offset (or LSO) of the partition. This is the last offset such that the state of all transactional records prior to this offset have been decided (ABORTED or COMMITTED)</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset.</td></tr>
+<tr>
+<td>aborted_transactions</td><td>null</td></tr>
+<tr>
+<td>producer_id</td><td>The producer id associated with the aborted transactions</td></tr>
+<tr>
+<td>first_offset</td><td>The first offset in the aborted transaction</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 8) => throttle_time_ms error_code session_id [responses] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  session_id => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark last_stable_offset log_start_offset [aborted_transactions] 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+        last_stable_offset => INT64
+        log_start_offset => INT64
+        aborted_transactions => producer_id first_offset 
+          producer_id => INT64
+          first_offset => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>session_id</td><td>The fetch session ID</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>last_stable_offset</td><td>The last stable offset (or LSO) of the partition. This is the last offset such that the state of all transactional records prior to this offset have been decided (ABORTED or COMMITTED)</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset.</td></tr>
+<tr>
+<td>aborted_transactions</td><td>null</td></tr>
+<tr>
+<td>producer_id</td><td>The producer id associated with the aborted transactions</td></tr>
+<tr>
+<td>first_offset</td><td>The first offset in the aborted transaction</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 9) => throttle_time_ms error_code session_id [responses] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  session_id => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark last_stable_offset log_start_offset [aborted_transactions] 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+        last_stable_offset => INT64
+        log_start_offset => INT64
+        aborted_transactions => producer_id first_offset 
+          producer_id => INT64
+          first_offset => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>session_id</td><td>The fetch session ID</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>last_stable_offset</td><td>The last stable offset (or LSO) of the partition. This is the last offset such that the state of all transactional records prior to this offset have been decided (ABORTED or COMMITTED)</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset.</td></tr>
+<tr>
+<td>aborted_transactions</td><td>null</td></tr>
+<tr>
+<td>producer_id</td><td>The producer id associated with the aborted transactions</td></tr>
+<tr>
+<td>first_offset</td><td>The first offset in the aborted transaction</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>Fetch Response (Version: 10) => throttle_time_ms error_code session_id [responses] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  session_id => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition_header record_set 
+      partition_header => partition error_code high_watermark last_stable_offset log_start_offset [aborted_transactions] 
+        partition => INT32
+        error_code => INT16
+        high_watermark => INT64
+        last_stable_offset => INT64
+        log_start_offset => INT64
+        aborted_transactions => producer_id first_offset 
+          producer_id => INT64
+          first_offset => INT64
+      record_set => RECORDS
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>session_id</td><td>The fetch session ID</td></tr>
+<tr>
+<td>responses</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>null</td></tr>
+<tr>
+<td>partition_header</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>high_watermark</td><td>Last committed offset.</td></tr>
+<tr>
+<td>last_stable_offset</td><td>The last stable offset (or LSO) of the partition. This is the last offset such that the state of all transactional records prior to this offset have been decided (ABORTED or COMMITTED)</td></tr>
+<tr>
+<td>log_start_offset</td><td>Earliest available offset.</td></tr>
+<tr>
+<td>aborted_transactions</td><td>null</td></tr>
+<tr>
+<td>producer_id</td><td>The producer id associated with the aborted transactions</td></tr>
+<tr>
+<td>first_offset</td><td>The first offset in the aborted transaction</td></tr>
+<tr>
+<td>record_set</td><td>null</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_ListOffsets">ListOffsets API (Key: 2):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>ListOffsets Request (Version: 0) => replica_id [topics] 
+  replica_id => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition timestamp max_num_offsets 
+      partition => INT32
+      timestamp => INT64
+      max_num_offsets => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>topics</td><td>Topics to list offsets.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to list offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>timestamp</td><td>The target timestamp for the partition.</td></tr>
+<tr>
+<td>max_num_offsets</td><td>Maximum offsets to return.</td></tr>
+</table>
+</p>
+<p><pre>ListOffsets Request (Version: 1) => replica_id [topics] 
+  replica_id => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition timestamp 
+      partition => INT32
+      timestamp => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>topics</td><td>Topics to list offsets.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to list offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>timestamp</td><td>The target timestamp for the partition.</td></tr>
+</table>
+</p>
+<p><pre>ListOffsets Request (Version: 2) => replica_id isolation_level [topics] 
+  replica_id => INT32
+  isolation_level => INT8
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition timestamp 
+      partition => INT32
+      timestamp => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>topics</td><td>Topics to list offsets.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to list offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>timestamp</td><td>The target timestamp for the partition.</td></tr>
+</table>
+</p>
+<p><pre>ListOffsets Request (Version: 3) => replica_id isolation_level [topics] 
+  replica_id => INT32
+  isolation_level => INT8
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition timestamp 
+      partition => INT32
+      timestamp => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>topics</td><td>Topics to list offsets.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to list offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>timestamp</td><td>The target timestamp for the partition.</td></tr>
+</table>
+</p>
+<p><pre>ListOffsets Request (Version: 4) => replica_id isolation_level [topics] 
+  replica_id => INT32
+  isolation_level => INT8
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition current_leader_epoch timestamp 
+      partition => INT32
+      current_leader_epoch => INT32
+      timestamp => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>replica_id</td><td>Broker id of the follower. For normal consumers, use -1.</td></tr>
+<tr>
+<td>isolation_level</td><td>This setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to [...]
+<tr>
+<td>topics</td><td>Topics to list offsets.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to list offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>current_leader_epoch</td><td>The current leader epoch, if provided, is used to fence consumers/replicas with old metadata. If the epoch provided by the client is larger than the current epoch known to the broker, then the UNKNOWN_LEADER_EPOCH error code will be returned. If the provided epoch is smaller, then the FENCED_LEADER_EPOCH error code will be returned.</td></tr>
+<tr>
+<td>timestamp</td><td>The target timestamp for the partition.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>ListOffsets Response (Version: 0) => [responses] 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code [offsets'] 
+      partition => INT32
+      error_code => INT16
+      offsets' => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>The listed offsets by topic</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>The listed offsets by partition</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>offsets'</td><td>A list of offsets.</td></tr>
+</table>
+</p>
+<p><pre>ListOffsets Response (Version: 1) => [responses] 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code timestamp offset 
+      partition => INT32
+      error_code => INT16
+      timestamp => INT64
+      offset => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>The listed offsets by topic</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>The listed offsets by partition</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>timestamp</td><td>The timestamp associated with the returned offset</td></tr>
+<tr>
+<td>offset</td><td>The offset found</td></tr>
+</table>
+</p>
+<p><pre>ListOffsets Response (Version: 2) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code timestamp offset 
+      partition => INT32
+      error_code => INT16
+      timestamp => INT64
+      offset => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>The listed offsets by topic</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>The listed offsets by partition</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>timestamp</td><td>The timestamp associated with the returned offset</td></tr>
+<tr>
+<td>offset</td><td>The offset found</td></tr>
+</table>
+</p>
+<p><pre>ListOffsets Response (Version: 3) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code timestamp offset 
+      partition => INT32
+      error_code => INT16
+      timestamp => INT64
+      offset => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>The listed offsets by topic</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>The listed offsets by partition</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>timestamp</td><td>The timestamp associated with the returned offset</td></tr>
+<tr>
+<td>offset</td><td>The offset found</td></tr>
+</table>
+</p>
+<p><pre>ListOffsets Response (Version: 4) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code timestamp offset leader_epoch 
+      partition => INT32
+      error_code => INT16
+      timestamp => INT64
+      offset => INT64
+      leader_epoch => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>The listed offsets by topic</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>The listed offsets by partition</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>timestamp</td><td>The timestamp associated with the returned offset</td></tr>
+<tr>
+<td>offset</td><td>The offset found</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_Metadata">Metadata API (Key: 3):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>Metadata Request (Version: 0) => [topics] 
+  topics => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to fetch metadata for. If no topics are specified fetch metadata for all topics.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Request (Version: 1) => [topics] 
+  topics => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to fetch metadata for. If the topics array is null fetch metadata for all topics.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Request (Version: 2) => [topics] 
+  topics => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to fetch metadata for. If the topics array is null fetch metadata for all topics.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Request (Version: 3) => [topics] 
+  topics => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to fetch metadata for. If the topics array is null fetch metadata for all topics.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Request (Version: 4) => [topics] allow_auto_topic_creation 
+  topics => STRING
+  allow_auto_topic_creation => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to fetch metadata for. If the topics array is null fetch metadata for all topics.</td></tr>
+<tr>
+<td>allow_auto_topic_creation</td><td>If this and the broker config <code>auto.create.topics.enable</code> are true, topics that don't exist will be created by the broker. Otherwise, no topics will be created by the broker.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Request (Version: 5) => [topics] allow_auto_topic_creation 
+  topics => STRING
+  allow_auto_topic_creation => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to fetch metadata for. If the topics array is null fetch metadata for all topics.</td></tr>
+<tr>
+<td>allow_auto_topic_creation</td><td>If this and the broker config <code>auto.create.topics.enable</code> are true, topics that don't exist will be created by the broker. Otherwise, no topics will be created by the broker.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Request (Version: 6) => [topics] allow_auto_topic_creation 
+  topics => STRING
+  allow_auto_topic_creation => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to fetch metadata for. If the topics array is null fetch metadata for all topics.</td></tr>
+<tr>
+<td>allow_auto_topic_creation</td><td>If this and the broker config <code>auto.create.topics.enable</code> are true, topics that don't exist will be created by the broker. Otherwise, no topics will be created by the broker.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Request (Version: 7) => [topics] allow_auto_topic_creation 
+  topics => STRING
+  allow_auto_topic_creation => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to fetch metadata for. If the topics array is null fetch metadata for all topics.</td></tr>
+<tr>
+<td>allow_auto_topic_creation</td><td>If this and the broker config <code>auto.create.topics.enable</code> are true, topics that don't exist will be created by the broker. Otherwise, no topics will be created by the broker.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>Metadata Response (Version: 0) => [brokers] [topic_metadata] 
+  brokers => node_id host port 
+    node_id => INT32
+    host => STRING
+    port => INT32
+  topic_metadata => error_code topic [partition_metadata] 
+    error_code => INT16
+    topic => STRING
+    partition_metadata => error_code partition leader [replicas] [isr] 
+      error_code => INT16
+      partition => INT32
+      leader => INT32
+      replicas => INT32
+      isr => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>brokers</td><td>Host and port information for all brokers.</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>topic_metadata</td><td>Metadata for requested topics</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_metadata</td><td>Metadata for each partition of the topic.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader</td><td>The id of the broker acting as leader for this partition.</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that host this partition.</td></tr>
+<tr>
+<td>isr</td><td>The set of nodes that are in sync with the leader for this partition.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Response (Version: 1) => [brokers] controller_id [topic_metadata] 
+  brokers => node_id host port rack 
+    node_id => INT32
+    host => STRING
+    port => INT32
+    rack => NULLABLE_STRING
+  controller_id => INT32
+  topic_metadata => error_code topic is_internal [partition_metadata] 
+    error_code => INT16
+    topic => STRING
+    is_internal => BOOLEAN
+    partition_metadata => error_code partition leader [replicas] [isr] 
+      error_code => INT16
+      partition => INT32
+      leader => INT32
+      replicas => INT32
+      isr => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>brokers</td><td>Host and port information for all brokers.</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>rack</td><td>The rack of the broker.</td></tr>
+<tr>
+<td>controller_id</td><td>The broker id of the controller broker.</td></tr>
+<tr>
+<td>topic_metadata</td><td>Metadata for requested topics</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>is_internal</td><td>Indicates if the topic is considered a Kafka internal topic</td></tr>
+<tr>
+<td>partition_metadata</td><td>Metadata for each partition of the topic.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader</td><td>The id of the broker acting as leader for this partition.</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that host this partition.</td></tr>
+<tr>
+<td>isr</td><td>The set of nodes that are in sync with the leader for this partition.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Response (Version: 2) => [brokers] cluster_id controller_id [topic_metadata] 
+  brokers => node_id host port rack 
+    node_id => INT32
+    host => STRING
+    port => INT32
+    rack => NULLABLE_STRING
+  cluster_id => NULLABLE_STRING
+  controller_id => INT32
+  topic_metadata => error_code topic is_internal [partition_metadata] 
+    error_code => INT16
+    topic => STRING
+    is_internal => BOOLEAN
+    partition_metadata => error_code partition leader [replicas] [isr] 
+      error_code => INT16
+      partition => INT32
+      leader => INT32
+      replicas => INT32
+      isr => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>brokers</td><td>Host and port information for all brokers.</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>rack</td><td>The rack of the broker.</td></tr>
+<tr>
+<td>cluster_id</td><td>The cluster id that this broker belongs to.</td></tr>
+<tr>
+<td>controller_id</td><td>The broker id of the controller broker.</td></tr>
+<tr>
+<td>topic_metadata</td><td>Metadata for requested topics</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>is_internal</td><td>Indicates if the topic is considered a Kafka internal topic</td></tr>
+<tr>
+<td>partition_metadata</td><td>Metadata for each partition of the topic.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader</td><td>The id of the broker acting as leader for this partition.</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that host this partition.</td></tr>
+<tr>
+<td>isr</td><td>The set of nodes that are in sync with the leader for this partition.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Response (Version: 3) => throttle_time_ms [brokers] cluster_id controller_id [topic_metadata] 
+  throttle_time_ms => INT32
+  brokers => node_id host port rack 
+    node_id => INT32
+    host => STRING
+    port => INT32
+    rack => NULLABLE_STRING
+  cluster_id => NULLABLE_STRING
+  controller_id => INT32
+  topic_metadata => error_code topic is_internal [partition_metadata] 
+    error_code => INT16
+    topic => STRING
+    is_internal => BOOLEAN
+    partition_metadata => error_code partition leader [replicas] [isr] 
+      error_code => INT16
+      partition => INT32
+      leader => INT32
+      replicas => INT32
+      isr => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>brokers</td><td>Host and port information for all brokers.</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>rack</td><td>The rack of the broker.</td></tr>
+<tr>
+<td>cluster_id</td><td>The cluster id that this broker belongs to.</td></tr>
+<tr>
+<td>controller_id</td><td>The broker id of the controller broker.</td></tr>
+<tr>
+<td>topic_metadata</td><td>Metadata for requested topics</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>is_internal</td><td>Indicates if the topic is considered a Kafka internal topic</td></tr>
+<tr>
+<td>partition_metadata</td><td>Metadata for each partition of the topic.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader</td><td>The id of the broker acting as leader for this partition.</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that host this partition.</td></tr>
+<tr>
+<td>isr</td><td>The set of nodes that are in sync with the leader for this partition.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Response (Version: 4) => throttle_time_ms [brokers] cluster_id controller_id [topic_metadata] 
+  throttle_time_ms => INT32
+  brokers => node_id host port rack 
+    node_id => INT32
+    host => STRING
+    port => INT32
+    rack => NULLABLE_STRING
+  cluster_id => NULLABLE_STRING
+  controller_id => INT32
+  topic_metadata => error_code topic is_internal [partition_metadata] 
+    error_code => INT16
+    topic => STRING
+    is_internal => BOOLEAN
+    partition_metadata => error_code partition leader [replicas] [isr] 
+      error_code => INT16
+      partition => INT32
+      leader => INT32
+      replicas => INT32
+      isr => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>brokers</td><td>Host and port information for all brokers.</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>rack</td><td>The rack of the broker.</td></tr>
+<tr>
+<td>cluster_id</td><td>The cluster id that this broker belongs to.</td></tr>
+<tr>
+<td>controller_id</td><td>The broker id of the controller broker.</td></tr>
+<tr>
+<td>topic_metadata</td><td>Metadata for requested topics</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>is_internal</td><td>Indicates if the topic is considered a Kafka internal topic</td></tr>
+<tr>
+<td>partition_metadata</td><td>Metadata for each partition of the topic.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader</td><td>The id of the broker acting as leader for this partition.</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that host this partition.</td></tr>
+<tr>
+<td>isr</td><td>The set of nodes that are in sync with the leader for this partition.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Response (Version: 5) => throttle_time_ms [brokers] cluster_id controller_id [topic_metadata] 
+  throttle_time_ms => INT32
+  brokers => node_id host port rack 
+    node_id => INT32
+    host => STRING
+    port => INT32
+    rack => NULLABLE_STRING
+  cluster_id => NULLABLE_STRING
+  controller_id => INT32
+  topic_metadata => error_code topic is_internal [partition_metadata] 
+    error_code => INT16
+    topic => STRING
+    is_internal => BOOLEAN
+    partition_metadata => error_code partition leader [replicas] [isr] [offline_replicas] 
+      error_code => INT16
+      partition => INT32
+      leader => INT32
+      replicas => INT32
+      isr => INT32
+      offline_replicas => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>brokers</td><td>Host and port information for all brokers.</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>rack</td><td>The rack of the broker.</td></tr>
+<tr>
+<td>cluster_id</td><td>The cluster id that this broker belongs to.</td></tr>
+<tr>
+<td>controller_id</td><td>The broker id of the controller broker.</td></tr>
+<tr>
+<td>topic_metadata</td><td>Metadata for requested topics</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>is_internal</td><td>Indicates if the topic is considered a Kafka internal topic</td></tr>
+<tr>
+<td>partition_metadata</td><td>Metadata for each partition of the topic.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader</td><td>The id of the broker acting as leader for this partition.</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that host this partition.</td></tr>
+<tr>
+<td>isr</td><td>The set of nodes that are in sync with the leader for this partition.</td></tr>
+<tr>
+<td>offline_replicas</td><td>The set of offline replicas of this partition.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Response (Version: 6) => throttle_time_ms [brokers] cluster_id controller_id [topic_metadata] 
+  throttle_time_ms => INT32
+  brokers => node_id host port rack 
+    node_id => INT32
+    host => STRING
+    port => INT32
+    rack => NULLABLE_STRING
+  cluster_id => NULLABLE_STRING
+  controller_id => INT32
+  topic_metadata => error_code topic is_internal [partition_metadata] 
+    error_code => INT16
+    topic => STRING
+    is_internal => BOOLEAN
+    partition_metadata => error_code partition leader [replicas] [isr] [offline_replicas] 
+      error_code => INT16
+      partition => INT32
+      leader => INT32
+      replicas => INT32
+      isr => INT32
+      offline_replicas => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>brokers</td><td>Host and port information for all brokers.</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>rack</td><td>The rack of the broker.</td></tr>
+<tr>
+<td>cluster_id</td><td>The cluster id that this broker belongs to.</td></tr>
+<tr>
+<td>controller_id</td><td>The broker id of the controller broker.</td></tr>
+<tr>
+<td>topic_metadata</td><td>Metadata for requested topics</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>is_internal</td><td>Indicates if the topic is considered a Kafka internal topic</td></tr>
+<tr>
+<td>partition_metadata</td><td>Metadata for each partition of the topic.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader</td><td>The id of the broker acting as leader for this partition.</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that host this partition.</td></tr>
+<tr>
+<td>isr</td><td>The set of nodes that are in sync with the leader for this partition.</td></tr>
+<tr>
+<td>offline_replicas</td><td>The set of offline replicas of this partition.</td></tr>
+</table>
+</p>
+<p><pre>Metadata Response (Version: 7) => throttle_time_ms [brokers] cluster_id controller_id [topic_metadata] 
+  throttle_time_ms => INT32
+  brokers => node_id host port rack 
+    node_id => INT32
+    host => STRING
+    port => INT32
+    rack => NULLABLE_STRING
+  cluster_id => NULLABLE_STRING
+  controller_id => INT32
+  topic_metadata => error_code topic is_internal [partition_metadata] 
+    error_code => INT16
+    topic => STRING
+    is_internal => BOOLEAN
+    partition_metadata => error_code partition leader leader_epoch [replicas] [isr] [offline_replicas] 
+      error_code => INT16
+      partition => INT32
+      leader => INT32
+      leader_epoch => INT32
+      replicas => INT32
+      isr => INT32
+      offline_replicas => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>brokers</td><td>Host and port information for all brokers.</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>rack</td><td>The rack of the broker.</td></tr>
+<tr>
+<td>cluster_id</td><td>The cluster id that this broker belongs to.</td></tr>
+<tr>
+<td>controller_id</td><td>The broker id of the controller broker.</td></tr>
+<tr>
+<td>topic_metadata</td><td>Metadata for requested topics</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>is_internal</td><td>Indicates if the topic is considered a Kafka internal topic</td></tr>
+<tr>
+<td>partition_metadata</td><td>Metadata for each partition of the topic.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader</td><td>The id of the broker acting as leader for this partition.</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that host this partition.</td></tr>
+<tr>
+<td>isr</td><td>The set of nodes that are in sync with the leader for this partition.</td></tr>
+<tr>
+<td>offline_replicas</td><td>The set of offline replicas of this partition.</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_LeaderAndIsr">LeaderAndIsr API (Key: 4):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>LeaderAndIsr Request (Version: 0) => controller_id controller_epoch [partition_states] [live_leaders] 
+  controller_id => INT32
+  controller_epoch => INT32
+  partition_states => topic partition controller_epoch leader leader_epoch [isr] zk_version [replicas] 
+    topic => STRING
+    partition => INT32
+    controller_epoch => INT32
+    leader => INT32
+    leader_epoch => INT32
+    isr => INT32
+    zk_version => INT32
+    replicas => INT32
+  live_leaders => id host port 
+    id => INT32
+    host => STRING
+    port => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>controller_id</td><td>The controller id.</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>partition_states</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>leader</td><td>The broker id for the leader.</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch.</td></tr>
+<tr>
+<td>isr</td><td>The in sync replica ids.</td></tr>
+<tr>
+<td>zk_version</td><td>The ZK version.</td></tr>
+<tr>
+<td>replicas</td><td>The replica ids.</td></tr>
+<tr>
+<td>live_leaders</td><td>null</td></tr>
+<tr>
+<td>id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+</table>
+</p>
+<p><pre>LeaderAndIsr Request (Version: 1) => controller_id controller_epoch [partition_states] [live_leaders] 
+  controller_id => INT32
+  controller_epoch => INT32
+  partition_states => topic partition controller_epoch leader leader_epoch [isr] zk_version [replicas] is_new 
+    topic => STRING
+    partition => INT32
+    controller_epoch => INT32
+    leader => INT32
+    leader_epoch => INT32
+    isr => INT32
+    zk_version => INT32
+    replicas => INT32
+    is_new => BOOLEAN
+  live_leaders => id host port 
+    id => INT32
+    host => STRING
+    port => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>controller_id</td><td>The controller id.</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>partition_states</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>leader</td><td>The broker id for the leader.</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch.</td></tr>
+<tr>
+<td>isr</td><td>The in sync replica ids.</td></tr>
+<tr>
+<td>zk_version</td><td>The ZK version.</td></tr>
+<tr>
+<td>replicas</td><td>The replica ids.</td></tr>
+<tr>
+<td>is_new</td><td>Whether the replica should have existed on the broker or not</td></tr>
+<tr>
+<td>live_leaders</td><td>null</td></tr>
+<tr>
+<td>id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>LeaderAndIsr Response (Version: 0) => error_code [partitions] 
+  error_code => INT16
+  partitions => topic partition error_code 
+    topic => STRING
+    partition => INT32
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>LeaderAndIsr Response (Version: 1) => error_code [partitions] 
+  error_code => INT16
+  partitions => topic partition error_code 
+    topic => STRING
+    partition => INT32
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_StopReplica">StopReplica API (Key: 5):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>StopReplica Request (Version: 0) => controller_id controller_epoch delete_partitions [partitions] 
+  controller_id => INT32
+  controller_epoch => INT32
+  delete_partitions => BOOLEAN
+  partitions => topic partition 
+    topic => STRING
+    partition => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>controller_id</td><td>The controller id.</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>delete_partitions</td><td>Boolean which indicates if replica's partitions must be deleted.</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>StopReplica Response (Version: 0) => error_code [partitions] 
+  error_code => INT16
+  partitions => topic partition error_code 
+    topic => STRING
+    partition => INT32
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_UpdateMetadata">UpdateMetadata API (Key: 6):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>UpdateMetadata Request (Version: 0) => controller_id controller_epoch [partition_states] [live_brokers] 
+  controller_id => INT32
+  controller_epoch => INT32
+  partition_states => topic partition controller_epoch leader leader_epoch [isr] zk_version [replicas] 
+    topic => STRING
+    partition => INT32
+    controller_epoch => INT32
+    leader => INT32
+    leader_epoch => INT32
+    isr => INT32
+    zk_version => INT32
+    replicas => INT32
+  live_brokers => id host port 
+    id => INT32
+    host => STRING
+    port => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>controller_id</td><td>The controller id.</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>partition_states</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>leader</td><td>The broker id for the leader.</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch.</td></tr>
+<tr>
+<td>isr</td><td>The in sync replica ids.</td></tr>
+<tr>
+<td>zk_version</td><td>The ZK version.</td></tr>
+<tr>
+<td>replicas</td><td>The replica ids.</td></tr>
+<tr>
+<td>live_brokers</td><td>null</td></tr>
+<tr>
+<td>id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+</table>
+</p>
+<p><pre>UpdateMetadata Request (Version: 1) => controller_id controller_epoch [partition_states] [live_brokers] 
+  controller_id => INT32
+  controller_epoch => INT32
+  partition_states => topic partition controller_epoch leader leader_epoch [isr] zk_version [replicas] 
+    topic => STRING
+    partition => INT32
+    controller_epoch => INT32
+    leader => INT32
+    leader_epoch => INT32
+    isr => INT32
+    zk_version => INT32
+    replicas => INT32
+  live_brokers => id [end_points] 
+    id => INT32
+    end_points => port host security_protocol_type 
+      port => INT32
+      host => STRING
+      security_protocol_type => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>controller_id</td><td>The controller id.</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>partition_states</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>leader</td><td>The broker id for the leader.</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch.</td></tr>
+<tr>
+<td>isr</td><td>The in sync replica ids.</td></tr>
+<tr>
+<td>zk_version</td><td>The ZK version.</td></tr>
+<tr>
+<td>replicas</td><td>The replica ids.</td></tr>
+<tr>
+<td>live_brokers</td><td>null</td></tr>
+<tr>
+<td>id</td><td>The broker id.</td></tr>
+<tr>
+<td>end_points</td><td>null</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>security_protocol_type</td><td>The security protocol type.</td></tr>
+</table>
+</p>
+<p><pre>UpdateMetadata Request (Version: 2) => controller_id controller_epoch [partition_states] [live_brokers] 
+  controller_id => INT32
+  controller_epoch => INT32
+  partition_states => topic partition controller_epoch leader leader_epoch [isr] zk_version [replicas] 
+    topic => STRING
+    partition => INT32
+    controller_epoch => INT32
+    leader => INT32
+    leader_epoch => INT32
+    isr => INT32
+    zk_version => INT32
+    replicas => INT32
+  live_brokers => id [end_points] rack 
+    id => INT32
+    end_points => port host security_protocol_type 
+      port => INT32
+      host => STRING
+      security_protocol_type => INT16
+    rack => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>controller_id</td><td>The controller id.</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>partition_states</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>leader</td><td>The broker id for the leader.</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch.</td></tr>
+<tr>
+<td>isr</td><td>The in sync replica ids.</td></tr>
+<tr>
+<td>zk_version</td><td>The ZK version.</td></tr>
+<tr>
+<td>replicas</td><td>The replica ids.</td></tr>
+<tr>
+<td>live_brokers</td><td>null</td></tr>
+<tr>
+<td>id</td><td>The broker id.</td></tr>
+<tr>
+<td>end_points</td><td>null</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>security_protocol_type</td><td>The security protocol type.</td></tr>
+<tr>
+<td>rack</td><td>The rack</td></tr>
+</table>
+</p>
+<p><pre>UpdateMetadata Request (Version: 3) => controller_id controller_epoch [partition_states] [live_brokers] 
+  controller_id => INT32
+  controller_epoch => INT32
+  partition_states => topic partition controller_epoch leader leader_epoch [isr] zk_version [replicas] 
+    topic => STRING
+    partition => INT32
+    controller_epoch => INT32
+    leader => INT32
+    leader_epoch => INT32
+    isr => INT32
+    zk_version => INT32
+    replicas => INT32
+  live_brokers => id [end_points] rack 
+    id => INT32
+    end_points => port host listener_name security_protocol_type 
+      port => INT32
+      host => STRING
+      listener_name => STRING
+      security_protocol_type => INT16
+    rack => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>controller_id</td><td>The controller id.</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>partition_states</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>leader</td><td>The broker id for the leader.</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch.</td></tr>
+<tr>
+<td>isr</td><td>The in sync replica ids.</td></tr>
+<tr>
+<td>zk_version</td><td>The ZK version.</td></tr>
+<tr>
+<td>replicas</td><td>The replica ids.</td></tr>
+<tr>
+<td>live_brokers</td><td>null</td></tr>
+<tr>
+<td>id</td><td>The broker id.</td></tr>
+<tr>
+<td>end_points</td><td>null</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>listener_name</td><td>The listener name.</td></tr>
+<tr>
+<td>security_protocol_type</td><td>The security protocol type.</td></tr>
+<tr>
+<td>rack</td><td>The rack</td></tr>
+</table>
+</p>
+<p><pre>UpdateMetadata Request (Version: 4) => controller_id controller_epoch [partition_states] [live_brokers] 
+  controller_id => INT32
+  controller_epoch => INT32
+  partition_states => topic partition controller_epoch leader leader_epoch [isr] zk_version [replicas] [offline_replicas] 
+    topic => STRING
+    partition => INT32
+    controller_epoch => INT32
+    leader => INT32
+    leader_epoch => INT32
+    isr => INT32
+    zk_version => INT32
+    replicas => INT32
+    offline_replicas => INT32
+  live_brokers => id [end_points] rack 
+    id => INT32
+    end_points => port host listener_name security_protocol_type 
+      port => INT32
+      host => STRING
+      listener_name => STRING
+      security_protocol_type => INT16
+    rack => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>controller_id</td><td>The controller id.</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>partition_states</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>controller_epoch</td><td>The controller epoch.</td></tr>
+<tr>
+<td>leader</td><td>The broker id for the leader.</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch.</td></tr>
+<tr>
+<td>isr</td><td>The in sync replica ids.</td></tr>
+<tr>
+<td>zk_version</td><td>The ZK version.</td></tr>
+<tr>
+<td>replicas</td><td>The replica ids.</td></tr>
+<tr>
+<td>offline_replicas</td><td>The offline replica ids</td></tr>
+<tr>
+<td>live_brokers</td><td>null</td></tr>
+<tr>
+<td>id</td><td>The broker id.</td></tr>
+<tr>
+<td>end_points</td><td>null</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>listener_name</td><td>The listener name.</td></tr>
+<tr>
+<td>security_protocol_type</td><td>The security protocol type.</td></tr>
+<tr>
+<td>rack</td><td>The rack</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>UpdateMetadata Response (Version: 0) => error_code 
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>UpdateMetadata Response (Version: 1) => error_code 
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>UpdateMetadata Response (Version: 2) => error_code 
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>UpdateMetadata Response (Version: 3) => error_code 
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>UpdateMetadata Response (Version: 4) => error_code 
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_ControlledShutdown">ControlledShutdown API (Key: 7):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>ControlledShutdown Request (Version: 0) => broker_id 
+  broker_id => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>broker_id</td><td>The id of the broker for which controlled shutdown has been requested.</td></tr>
+</table>
+</p>
+<p><pre>ControlledShutdown Request (Version: 1) => broker_id 
+  broker_id => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>broker_id</td><td>The id of the broker for which controlled shutdown has been requested.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>ControlledShutdown Response (Version: 0) => error_code [partitions_remaining] 
+  error_code => INT16
+  partitions_remaining => topic partition 
+    topic => STRING
+    partition => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partitions_remaining</td><td>The partitions that the broker still leads.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+</table>
+</p>
+<p><pre>ControlledShutdown Response (Version: 1) => error_code [partitions_remaining] 
+  error_code => INT16
+  partitions_remaining => topic partition 
+    topic => STRING
+    partition => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partitions_remaining</td><td>The partitions that the broker still leads.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_OffsetCommit">OffsetCommit API (Key: 8):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>OffsetCommit Request (Version: 0) => group_id [topics] 
+  group_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset metadata 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Request (Version: 1) => group_id generation_id member_id [topics] 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset timestamp metadata 
+      partition => INT32
+      offset => INT64
+      timestamp => INT64
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>timestamp</td><td>Timestamp of the commit</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Request (Version: 2) => group_id generation_id member_id retention_time [topics] 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+  retention_time => INT64
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset metadata 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>retention_time</td><td>Time period in ms to retain the offset.</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Request (Version: 3) => group_id generation_id member_id retention_time [topics] 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+  retention_time => INT64
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset metadata 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>retention_time</td><td>Time period in ms to retain the offset.</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Request (Version: 4) => group_id generation_id member_id retention_time [topics] 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+  retention_time => INT64
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset metadata 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>retention_time</td><td>Time period in ms to retain the offset.</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Request (Version: 5) => group_id generation_id member_id [topics] 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset metadata 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Request (Version: 6) => group_id generation_id member_id [topics] 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset leader_epoch metadata 
+      partition => INT32
+      offset => INT64
+      leader_epoch => INT32
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch, if provided is derived from the last consumed record. This is used by the consumer to check for log truncation and to ensure partition metadata is up to date following a group rebalance.</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>OffsetCommit Response (Version: 0) => [responses] 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>Responses by topic for committed partitions</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses for committed partitions</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Response (Version: 1) => [responses] 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>Responses by topic for committed partitions</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses for committed partitions</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Response (Version: 2) => [responses] 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>Responses by topic for committed partitions</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses for committed partitions</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Response (Version: 3) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>Responses by topic for committed partitions</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses for committed partitions</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Response (Version: 4) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>Responses by topic for committed partitions</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses for committed partitions</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Response (Version: 5) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>Responses by topic for committed partitions</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses for committed partitions</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetCommit Response (Version: 6) => throttle_time_ms [responses] 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>Responses by topic for committed partitions</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses for committed partitions</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_OffsetFetch">OffsetFetch API (Key: 9):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>OffsetFetch Request (Version: 0) => group_id [topics] 
+  group_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition 
+      partition => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch offsets.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Request (Version: 1) => group_id [topics] 
+  group_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition 
+      partition => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch offsets.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Request (Version: 2) => group_id [topics] 
+  group_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition 
+      partition => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch offsets. If the topic array is null fetch offsets for all topics.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Request (Version: 3) => group_id [topics] 
+  group_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition 
+      partition => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch offsets. If the topic array is null fetch offsets for all topics.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Request (Version: 4) => group_id [topics] 
+  group_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition 
+      partition => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch offsets. If the topic array is null fetch offsets for all topics.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Request (Version: 5) => group_id [topics] 
+  group_id => STRING
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition 
+      partition => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>topics</td><td>Topics to fetch offsets. If the topic array is null fetch offsets for all topics.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to fetch offsets.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>OffsetFetch Response (Version: 0) => [responses] 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition offset metadata error_code 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>Responses by topic for fetched offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses by partition for fetched offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Response (Version: 1) => [responses] 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition offset metadata error_code 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>Responses by topic for fetched offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses by partition for fetched offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Response (Version: 2) => [responses] error_code 
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition offset metadata error_code 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+      error_code => INT16
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>responses</td><td>Responses by topic for fetched offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses by partition for fetched offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Response (Version: 3) => throttle_time_ms [responses] error_code 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition offset metadata error_code 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+      error_code => INT16
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>Responses by topic for fetched offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses by partition for fetched offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Response (Version: 4) => throttle_time_ms [responses] error_code 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition offset metadata error_code 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+      error_code => INT16
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>Responses by topic for fetched offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses by partition for fetched offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>OffsetFetch Response (Version: 5) => throttle_time_ms [responses] error_code 
+  throttle_time_ms => INT32
+  responses => topic [partition_responses] 
+    topic => STRING
+    partition_responses => partition offset leader_epoch metadata error_code 
+      partition => INT32
+      offset => INT64
+      leader_epoch => INT32
+      metadata => NULLABLE_STRING
+      error_code => INT16
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>responses</td><td>Responses by topic for fetched offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_responses</td><td>Responses by partition for fetched offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch, if provided is derived from the last consumed record. This is used by the consumer to check for log truncation and to ensure partition metadata is up to date following a group rebalance.</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_FindCoordinator">FindCoordinator API (Key: 10):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>FindCoordinator Request (Version: 0) => group_id 
+  group_id => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+</table>
+</p>
+<p><pre>FindCoordinator Request (Version: 1) => coordinator_key coordinator_type 
+  coordinator_key => STRING
+  coordinator_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>coordinator_key</td><td>Id to use for finding the coordinator (for groups, this is the groupId, for transactional producers, this is the transactional id)</td></tr>
+<tr>
+<td>coordinator_type</td><td>The type of coordinator to find (0 = group, 1 = transaction)</td></tr>
+</table>
+</p>
+<p><pre>FindCoordinator Request (Version: 2) => coordinator_key coordinator_type 
+  coordinator_key => STRING
+  coordinator_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>coordinator_key</td><td>Id to use for finding the coordinator (for groups, this is the groupId, for transactional producers, this is the transactional id)</td></tr>
+<tr>
+<td>coordinator_type</td><td>The type of coordinator to find (0 = group, 1 = transaction)</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>FindCoordinator Response (Version: 0) => error_code coordinator 
+  error_code => INT16
+  coordinator => node_id host port 
+    node_id => INT32
+    host => STRING
+    port => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>coordinator</td><td>Host and port information for the coordinator for a consumer group.</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+</table>
+</p>
+<p><pre>FindCoordinator Response (Version: 1) => throttle_time_ms error_code error_message coordinator 
+  throttle_time_ms => INT32
+  error_code => INT16
+  error_message => NULLABLE_STRING
+  coordinator => node_id host port 
+    node_id => INT32
+    host => STRING
+    port => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>coordinator</td><td>Host and port information for the coordinator</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+</table>
+</p>
+<p><pre>FindCoordinator Response (Version: 2) => throttle_time_ms error_code error_message coordinator 
+  throttle_time_ms => INT32
+  error_code => INT16
+  error_message => NULLABLE_STRING
+  coordinator => node_id host port 
+    node_id => INT32
+    host => STRING
+    port => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>coordinator</td><td>Host and port information for the coordinator</td></tr>
+<tr>
+<td>node_id</td><td>The broker id.</td></tr>
+<tr>
+<td>host</td><td>The hostname of the broker.</td></tr>
+<tr>
+<td>port</td><td>The port on which the broker accepts requests.</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_JoinGroup">JoinGroup API (Key: 11):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>JoinGroup Request (Version: 0) => group_id session_timeout member_id protocol_type [group_protocols] 
+  group_id => STRING
+  session_timeout => INT32
+  member_id => STRING
+  protocol_type => STRING
+  group_protocols => protocol_name protocol_metadata 
+    protocol_name => STRING
+    protocol_metadata => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>session_timeout</td><td>The coordinator considers the consumer dead if it receives no heartbeat after this timeout in ms.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>protocol_type</td><td>Unique name for class of protocols implemented by group</td></tr>
+<tr>
+<td>group_protocols</td><td>List of protocols that the member supports</td></tr>
+<tr>
+<td>protocol_name</td><td>null</td></tr>
+<tr>
+<td>protocol_metadata</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>JoinGroup Request (Version: 1) => group_id session_timeout rebalance_timeout member_id protocol_type [group_protocols] 
+  group_id => STRING
+  session_timeout => INT32
+  rebalance_timeout => INT32
+  member_id => STRING
+  protocol_type => STRING
+  group_protocols => protocol_name protocol_metadata 
+    protocol_name => STRING
+    protocol_metadata => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>session_timeout</td><td>The coordinator considers the consumer dead if it receives no heartbeat after this timeout in ms.</td></tr>
+<tr>
+<td>rebalance_timeout</td><td>The maximum time that the coordinator will wait for each member to rejoin when rebalancing the group</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>protocol_type</td><td>Unique name for class of protocols implemented by group</td></tr>
+<tr>
+<td>group_protocols</td><td>List of protocols that the member supports</td></tr>
+<tr>
+<td>protocol_name</td><td>null</td></tr>
+<tr>
+<td>protocol_metadata</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>JoinGroup Request (Version: 2) => group_id session_timeout rebalance_timeout member_id protocol_type [group_protocols] 
+  group_id => STRING
+  session_timeout => INT32
+  rebalance_timeout => INT32
+  member_id => STRING
+  protocol_type => STRING
+  group_protocols => protocol_name protocol_metadata 
+    protocol_name => STRING
+    protocol_metadata => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>session_timeout</td><td>The coordinator considers the consumer dead if it receives no heartbeat after this timeout in ms.</td></tr>
+<tr>
+<td>rebalance_timeout</td><td>The maximum time that the coordinator will wait for each member to rejoin when rebalancing the group</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>protocol_type</td><td>Unique name for class of protocols implemented by group</td></tr>
+<tr>
+<td>group_protocols</td><td>List of protocols that the member supports</td></tr>
+<tr>
+<td>protocol_name</td><td>null</td></tr>
+<tr>
+<td>protocol_metadata</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>JoinGroup Request (Version: 3) => group_id session_timeout rebalance_timeout member_id protocol_type [group_protocols] 
+  group_id => STRING
+  session_timeout => INT32
+  rebalance_timeout => INT32
+  member_id => STRING
+  protocol_type => STRING
+  group_protocols => protocol_name protocol_metadata 
+    protocol_name => STRING
+    protocol_metadata => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>session_timeout</td><td>The coordinator considers the consumer dead if it receives no heartbeat after this timeout in ms.</td></tr>
+<tr>
+<td>rebalance_timeout</td><td>The maximum time that the coordinator will wait for each member to rejoin when rebalancing the group</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>protocol_type</td><td>Unique name for class of protocols implemented by group</td></tr>
+<tr>
+<td>group_protocols</td><td>List of protocols that the member supports</td></tr>
+<tr>
+<td>protocol_name</td><td>null</td></tr>
+<tr>
+<td>protocol_metadata</td><td>null</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>JoinGroup Response (Version: 0) => error_code generation_id group_protocol leader_id member_id [members] 
+  error_code => INT16
+  generation_id => INT32
+  group_protocol => STRING
+  leader_id => STRING
+  member_id => STRING
+  members => member_id member_metadata 
+    member_id => STRING
+    member_metadata => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>group_protocol</td><td>The group protocol selected by the coordinator</td></tr>
+<tr>
+<td>leader_id</td><td>The leader of the group</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>members</td><td>null</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>member_metadata</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>JoinGroup Response (Version: 1) => error_code generation_id group_protocol leader_id member_id [members] 
+  error_code => INT16
+  generation_id => INT32
+  group_protocol => STRING
+  leader_id => STRING
+  member_id => STRING
+  members => member_id member_metadata 
+    member_id => STRING
+    member_metadata => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>group_protocol</td><td>The group protocol selected by the coordinator</td></tr>
+<tr>
+<td>leader_id</td><td>The leader of the group</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>members</td><td>null</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>member_metadata</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>JoinGroup Response (Version: 2) => throttle_time_ms error_code generation_id group_protocol leader_id member_id [members] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  generation_id => INT32
+  group_protocol => STRING
+  leader_id => STRING
+  member_id => STRING
+  members => member_id member_metadata 
+    member_id => STRING
+    member_metadata => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>group_protocol</td><td>The group protocol selected by the coordinator</td></tr>
+<tr>
+<td>leader_id</td><td>The leader of the group</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>members</td><td>null</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>member_metadata</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>JoinGroup Response (Version: 3) => throttle_time_ms error_code generation_id group_protocol leader_id member_id [members] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  generation_id => INT32
+  group_protocol => STRING
+  leader_id => STRING
+  member_id => STRING
+  members => member_id member_metadata 
+    member_id => STRING
+    member_metadata => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>group_protocol</td><td>The group protocol selected by the coordinator</td></tr>
+<tr>
+<td>leader_id</td><td>The leader of the group</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>members</td><td>null</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>member_metadata</td><td>null</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_Heartbeat">Heartbeat API (Key: 12):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>Heartbeat Request (Version: 0) => group_id generation_id member_id 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+</table>
+</p>
+<p><pre>Heartbeat Request (Version: 1) => group_id generation_id member_id 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+</table>
+</p>
+<p><pre>Heartbeat Request (Version: 2) => group_id generation_id member_id 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>Heartbeat Response (Version: 0) => error_code 
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>Heartbeat Response (Version: 1) => throttle_time_ms error_code 
+  throttle_time_ms => INT32
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>Heartbeat Response (Version: 2) => throttle_time_ms error_code 
+  throttle_time_ms => INT32
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_LeaveGroup">LeaveGroup API (Key: 13):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>LeaveGroup Request (Version: 0) => group_id member_id 
+  group_id => STRING
+  member_id => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+</table>
+</p>
+<p><pre>LeaveGroup Request (Version: 1) => group_id member_id 
+  group_id => STRING
+  member_id => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+</table>
+</p>
+<p><pre>LeaveGroup Request (Version: 2) => group_id member_id 
+  group_id => STRING
+  member_id => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>LeaveGroup Response (Version: 0) => error_code 
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>LeaveGroup Response (Version: 1) => throttle_time_ms error_code 
+  throttle_time_ms => INT32
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>LeaveGroup Response (Version: 2) => throttle_time_ms error_code 
+  throttle_time_ms => INT32
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_SyncGroup">SyncGroup API (Key: 14):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>SyncGroup Request (Version: 0) => group_id generation_id member_id [group_assignment] 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+  group_assignment => member_id member_assignment 
+    member_id => STRING
+    member_assignment => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>group_assignment</td><td>null</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>member_assignment</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>SyncGroup Request (Version: 1) => group_id generation_id member_id [group_assignment] 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+  group_assignment => member_id member_assignment 
+    member_id => STRING
+    member_assignment => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>group_assignment</td><td>null</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>member_assignment</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>SyncGroup Request (Version: 2) => group_id generation_id member_id [group_assignment] 
+  group_id => STRING
+  generation_id => INT32
+  member_id => STRING
+  group_assignment => member_id member_assignment 
+    member_id => STRING
+    member_assignment => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>generation_id</td><td>The generation of the group.</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>group_assignment</td><td>null</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>member_assignment</td><td>null</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>SyncGroup Response (Version: 0) => error_code member_assignment 
+  error_code => INT16
+  member_assignment => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>member_assignment</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>SyncGroup Response (Version: 1) => throttle_time_ms error_code member_assignment 
+  throttle_time_ms => INT32
+  error_code => INT16
+  member_assignment => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>member_assignment</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>SyncGroup Response (Version: 2) => throttle_time_ms error_code member_assignment 
+  throttle_time_ms => INT32
+  error_code => INT16
+  member_assignment => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>member_assignment</td><td>null</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_DescribeGroups">DescribeGroups API (Key: 15):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>DescribeGroups Request (Version: 0) => [group_ids] 
+  group_ids => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_ids</td><td>List of groupIds to request metadata for (an empty groupId array will return empty group metadata).</td></tr>
+</table>
+</p>
+<p><pre>DescribeGroups Request (Version: 1) => [group_ids] 
+  group_ids => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_ids</td><td>List of groupIds to request metadata for (an empty groupId array will return empty group metadata).</td></tr>
+</table>
+</p>
+<p><pre>DescribeGroups Request (Version: 2) => [group_ids] 
+  group_ids => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>group_ids</td><td>List of groupIds to request metadata for (an empty groupId array will return empty group metadata).</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>DescribeGroups Response (Version: 0) => [groups] 
+  groups => error_code group_id state protocol_type protocol [members] 
+    error_code => INT16
+    group_id => STRING
+    state => STRING
+    protocol_type => STRING
+    protocol => STRING
+    members => member_id client_id client_host member_metadata member_assignment 
+      member_id => STRING
+      client_id => STRING
+      client_host => STRING
+      member_metadata => BYTES
+      member_assignment => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>groups</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>state</td><td>The current state of the group (one of: Dead, Stable, CompletingRebalance, PreparingRebalance, or empty if there is no active group)</td></tr>
+<tr>
+<td>protocol_type</td><td>The current group protocol type (will be empty if there is no active group)</td></tr>
+<tr>
+<td>protocol</td><td>The current group protocol (only provided if the group is Stable)</td></tr>
+<tr>
+<td>members</td><td>Current group members (only provided if the group is not Dead)</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>client_id</td><td>The client id used in the member's latest join group request</td></tr>
+<tr>
+<td>client_host</td><td>The client host used in the request session corresponding to the member's join group.</td></tr>
+<tr>
+<td>member_metadata</td><td>The metadata corresponding to the current group protocol in use (will only be present if the group is stable).</td></tr>
+<tr>
+<td>member_assignment</td><td>The current assignment provided by the group leader (will only be present if the group is stable).</td></tr>
+</table>
+</p>
+<p><pre>DescribeGroups Response (Version: 1) => throttle_time_ms [groups] 
+  throttle_time_ms => INT32
+  groups => error_code group_id state protocol_type protocol [members] 
+    error_code => INT16
+    group_id => STRING
+    state => STRING
+    protocol_type => STRING
+    protocol => STRING
+    members => member_id client_id client_host member_metadata member_assignment 
+      member_id => STRING
+      client_id => STRING
+      client_host => STRING
+      member_metadata => BYTES
+      member_assignment => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>groups</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>state</td><td>The current state of the group (one of: Dead, Stable, CompletingRebalance, PreparingRebalance, or empty if there is no active group)</td></tr>
+<tr>
+<td>protocol_type</td><td>The current group protocol type (will be empty if there is no active group)</td></tr>
+<tr>
+<td>protocol</td><td>The current group protocol (only provided if the group is Stable)</td></tr>
+<tr>
+<td>members</td><td>Current group members (only provided if the group is not Dead)</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>client_id</td><td>The client id used in the member's latest join group request</td></tr>
+<tr>
+<td>client_host</td><td>The client host used in the request session corresponding to the member's join group.</td></tr>
+<tr>
+<td>member_metadata</td><td>The metadata corresponding to the current group protocol in use (will only be present if the group is stable).</td></tr>
+<tr>
+<td>member_assignment</td><td>The current assignment provided by the group leader (will only be present if the group is stable).</td></tr>
+</table>
+</p>
+<p><pre>DescribeGroups Response (Version: 2) => throttle_time_ms [groups] 
+  throttle_time_ms => INT32
+  groups => error_code group_id state protocol_type protocol [members] 
+    error_code => INT16
+    group_id => STRING
+    state => STRING
+    protocol_type => STRING
+    protocol => STRING
+    members => member_id client_id client_host member_metadata member_assignment 
+      member_id => STRING
+      client_id => STRING
+      client_host => STRING
+      member_metadata => BYTES
+      member_assignment => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>groups</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>state</td><td>The current state of the group (one of: Dead, Stable, CompletingRebalance, PreparingRebalance, or empty if there is no active group)</td></tr>
+<tr>
+<td>protocol_type</td><td>The current group protocol type (will be empty if there is no active group)</td></tr>
+<tr>
+<td>protocol</td><td>The current group protocol (only provided if the group is Stable)</td></tr>
+<tr>
+<td>members</td><td>Current group members (only provided if the group is not Dead)</td></tr>
+<tr>
+<td>member_id</td><td>The member id assigned by the group coordinator or null if joining for the first time.</td></tr>
+<tr>
+<td>client_id</td><td>The client id used in the member's latest join group request</td></tr>
+<tr>
+<td>client_host</td><td>The client host used in the request session corresponding to the member's join group.</td></tr>
+<tr>
+<td>member_metadata</td><td>The metadata corresponding to the current group protocol in use (will only be present if the group is stable).</td></tr>
+<tr>
+<td>member_assignment</td><td>The current assignment provided by the group leader (will only be present if the group is stable).</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_ListGroups">ListGroups API (Key: 16):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>ListGroups Request (Version: 0) => 
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr></table>
+</p>
+<p><pre>ListGroups Request (Version: 1) => 
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr></table>
+</p>
+<p><pre>ListGroups Request (Version: 2) => 
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr></table>
+</p>
+<b>Responses:</b><br>
+<p><pre>ListGroups Response (Version: 0) => error_code [groups] 
+  error_code => INT16
+  groups => group_id protocol_type 
+    group_id => STRING
+    protocol_type => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>groups</td><td>null</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>protocol_type</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>ListGroups Response (Version: 1) => throttle_time_ms error_code [groups] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  groups => group_id protocol_type 
+    group_id => STRING
+    protocol_type => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>groups</td><td>null</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>protocol_type</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>ListGroups Response (Version: 2) => throttle_time_ms error_code [groups] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  groups => group_id protocol_type 
+    group_id => STRING
+    protocol_type => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>groups</td><td>null</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>protocol_type</td><td>null</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_SaslHandshake">SaslHandshake API (Key: 17):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>SaslHandshake Request (Version: 0) => mechanism 
+  mechanism => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>mechanism</td><td>SASL Mechanism chosen by the client.</td></tr>
+</table>
+</p>
+<p><pre>SaslHandshake Request (Version: 1) => mechanism 
+  mechanism => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>mechanism</td><td>SASL Mechanism chosen by the client.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>SaslHandshake Response (Version: 0) => error_code [enabled_mechanisms] 
+  error_code => INT16
+  enabled_mechanisms => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>enabled_mechanisms</td><td>Array of mechanisms enabled in the server.</td></tr>
+</table>
+</p>
+<p><pre>SaslHandshake Response (Version: 1) => error_code [enabled_mechanisms] 
+  error_code => INT16
+  enabled_mechanisms => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>enabled_mechanisms</td><td>Array of mechanisms enabled in the server.</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_ApiVersions">ApiVersions API (Key: 18):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>ApiVersions Request (Version: 0) => 
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr></table>
+</p>
+<p><pre>ApiVersions Request (Version: 1) => 
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr></table>
+</p>
+<p><pre>ApiVersions Request (Version: 2) => 
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr></table>
+</p>
+<b>Responses:</b><br>
+<p><pre>ApiVersions Response (Version: 0) => error_code [api_versions] 
+  error_code => INT16
+  api_versions => api_key min_version max_version 
+    api_key => INT16
+    min_version => INT16
+    max_version => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>api_versions</td><td>API versions supported by the broker.</td></tr>
+<tr>
+<td>api_key</td><td>API key.</td></tr>
+<tr>
+<td>min_version</td><td>Minimum supported version.</td></tr>
+<tr>
+<td>max_version</td><td>Maximum supported version.</td></tr>
+</table>
+</p>
+<p><pre>ApiVersions Response (Version: 1) => error_code [api_versions] throttle_time_ms 
+  error_code => INT16
+  api_versions => api_key min_version max_version 
+    api_key => INT16
+    min_version => INT16
+    max_version => INT16
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>api_versions</td><td>API versions supported by the broker.</td></tr>
+<tr>
+<td>api_key</td><td>API key.</td></tr>
+<tr>
+<td>min_version</td><td>Minimum supported version.</td></tr>
+<tr>
+<td>max_version</td><td>Maximum supported version.</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>ApiVersions Response (Version: 2) => error_code [api_versions] throttle_time_ms 
+  error_code => INT16
+  api_versions => api_key min_version max_version 
+    api_key => INT16
+    min_version => INT16
+    max_version => INT16
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>api_versions</td><td>API versions supported by the broker.</td></tr>
+<tr>
+<td>api_key</td><td>API key.</td></tr>
+<tr>
+<td>min_version</td><td>Minimum supported version.</td></tr>
+<tr>
+<td>max_version</td><td>Maximum supported version.</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_CreateTopics">CreateTopics API (Key: 19):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>CreateTopics Request (Version: 0) => [create_topic_requests] timeout 
+  create_topic_requests => topic num_partitions replication_factor [replica_assignment] [config_entries] 
+    topic => STRING
+    num_partitions => INT32
+    replication_factor => INT16
+    replica_assignment => partition [replicas] 
+      partition => INT32
+      replicas => INT32
+    config_entries => config_name config_value 
+      config_name => STRING
+      config_value => NULLABLE_STRING
+  timeout => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>create_topic_requests</td><td>An array of single topic creation requests. Can not have multiple entries for the same topic.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>num_partitions</td><td>Number of partitions to be created. -1 indicates unset.</td></tr>
+<tr>
+<td>replication_factor</td><td>Replication factor for the topic. -1 indicates unset.</td></tr>
+<tr>
+<td>replica_assignment</td><td>Replica assignment among kafka brokers for this topic partitions. If this is set num_partitions and replication_factor must be unset.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that should host this partition. The first replica in the list is the preferred leader.</td></tr>
+<tr>
+<td>config_entries</td><td>Topic level configuration for topic to be set.</td></tr>
+<tr>
+<td>config_name</td><td>Configuration name</td></tr>
+<tr>
+<td>config_value</td><td>Configuration value</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for a topic to be completely created on the controller node. Values <= 0 will trigger topic creation and return immediately</td></tr>
+</table>
+</p>
+<p><pre>CreateTopics Request (Version: 1) => [create_topic_requests] timeout validate_only 
+  create_topic_requests => topic num_partitions replication_factor [replica_assignment] [config_entries] 
+    topic => STRING
+    num_partitions => INT32
+    replication_factor => INT16
+    replica_assignment => partition [replicas] 
+      partition => INT32
+      replicas => INT32
+    config_entries => config_name config_value 
+      config_name => STRING
+      config_value => NULLABLE_STRING
+  timeout => INT32
+  validate_only => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>create_topic_requests</td><td>An array of single topic creation requests. Can not have multiple entries for the same topic.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>num_partitions</td><td>Number of partitions to be created. -1 indicates unset.</td></tr>
+<tr>
+<td>replication_factor</td><td>Replication factor for the topic. -1 indicates unset.</td></tr>
+<tr>
+<td>replica_assignment</td><td>Replica assignment among kafka brokers for this topic partitions. If this is set num_partitions and replication_factor must be unset.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that should host this partition. The first replica in the list is the preferred leader.</td></tr>
+<tr>
+<td>config_entries</td><td>Topic level configuration for topic to be set.</td></tr>
+<tr>
+<td>config_name</td><td>Configuration name</td></tr>
+<tr>
+<td>config_value</td><td>Configuration value</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for a topic to be completely created on the controller node. Values <= 0 will trigger topic creation and return immediately</td></tr>
+<tr>
+<td>validate_only</td><td>If this is true, the request will be validated, but the topic won't be created.</td></tr>
+</table>
+</p>
+<p><pre>CreateTopics Request (Version: 2) => [create_topic_requests] timeout validate_only 
+  create_topic_requests => topic num_partitions replication_factor [replica_assignment] [config_entries] 
+    topic => STRING
+    num_partitions => INT32
+    replication_factor => INT16
+    replica_assignment => partition [replicas] 
+      partition => INT32
+      replicas => INT32
+    config_entries => config_name config_value 
+      config_name => STRING
+      config_value => NULLABLE_STRING
+  timeout => INT32
+  validate_only => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>create_topic_requests</td><td>An array of single topic creation requests. Can not have multiple entries for the same topic.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>num_partitions</td><td>Number of partitions to be created. -1 indicates unset.</td></tr>
+<tr>
+<td>replication_factor</td><td>Replication factor for the topic. -1 indicates unset.</td></tr>
+<tr>
+<td>replica_assignment</td><td>Replica assignment among kafka brokers for this topic partitions. If this is set num_partitions and replication_factor must be unset.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that should host this partition. The first replica in the list is the preferred leader.</td></tr>
+<tr>
+<td>config_entries</td><td>Topic level configuration for topic to be set.</td></tr>
+<tr>
+<td>config_name</td><td>Configuration name</td></tr>
+<tr>
+<td>config_value</td><td>Configuration value</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for a topic to be completely created on the controller node. Values <= 0 will trigger topic creation and return immediately</td></tr>
+<tr>
+<td>validate_only</td><td>If this is true, the request will be validated, but the topic won't be created.</td></tr>
+</table>
+</p>
+<p><pre>CreateTopics Request (Version: 3) => [create_topic_requests] timeout validate_only 
+  create_topic_requests => topic num_partitions replication_factor [replica_assignment] [config_entries] 
+    topic => STRING
+    num_partitions => INT32
+    replication_factor => INT16
+    replica_assignment => partition [replicas] 
+      partition => INT32
+      replicas => INT32
+    config_entries => config_name config_value 
+      config_name => STRING
+      config_value => NULLABLE_STRING
+  timeout => INT32
+  validate_only => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>create_topic_requests</td><td>An array of single topic creation requests. Can not have multiple entries for the same topic.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>num_partitions</td><td>Number of partitions to be created. -1 indicates unset.</td></tr>
+<tr>
+<td>replication_factor</td><td>Replication factor for the topic. -1 indicates unset.</td></tr>
+<tr>
+<td>replica_assignment</td><td>Replica assignment among kafka brokers for this topic partitions. If this is set num_partitions and replication_factor must be unset.</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>replicas</td><td>The set of all nodes that should host this partition. The first replica in the list is the preferred leader.</td></tr>
+<tr>
+<td>config_entries</td><td>Topic level configuration for topic to be set.</td></tr>
+<tr>
+<td>config_name</td><td>Configuration name</td></tr>
+<tr>
+<td>config_value</td><td>Configuration value</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for a topic to be completely created on the controller node. Values <= 0 will trigger topic creation and return immediately</td></tr>
+<tr>
+<td>validate_only</td><td>If this is true, the request will be validated, but the topic won't be created.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>CreateTopics Response (Version: 0) => [topic_errors] 
+  topic_errors => topic error_code 
+    topic => STRING
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topic_errors</td><td>An array of per topic error codes.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>CreateTopics Response (Version: 1) => [topic_errors] 
+  topic_errors => topic error_code error_message 
+    topic => STRING
+    error_code => INT16
+    error_message => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topic_errors</td><td>An array of per topic errors.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+</table>
+</p>
+<p><pre>CreateTopics Response (Version: 2) => throttle_time_ms [topic_errors] 
+  throttle_time_ms => INT32
+  topic_errors => topic error_code error_message 
+    topic => STRING
+    error_code => INT16
+    error_message => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topic_errors</td><td>An array of per topic errors.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+</table>
+</p>
+<p><pre>CreateTopics Response (Version: 3) => throttle_time_ms [topic_errors] 
+  throttle_time_ms => INT32
+  topic_errors => topic error_code error_message 
+    topic => STRING
+    error_code => INT16
+    error_message => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topic_errors</td><td>An array of per topic errors.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_DeleteTopics">DeleteTopics API (Key: 20):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>DeleteTopics Request (Version: 0) => [topics] timeout 
+  topics => STRING
+  timeout => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to be deleted.</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for a topic to be completely deleted on the controller node. Values <= 0 will trigger topic deletion and return immediately</td></tr>
+</table>
+</p>
+<p><pre>DeleteTopics Request (Version: 1) => [topics] timeout 
+  topics => STRING
+  timeout => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to be deleted.</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for a topic to be completely deleted on the controller node. Values <= 0 will trigger topic deletion and return immediately</td></tr>
+</table>
+</p>
+<p><pre>DeleteTopics Request (Version: 2) => [topics] timeout 
+  topics => STRING
+  timeout => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to be deleted.</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for a topic to be completely deleted on the controller node. Values <= 0 will trigger topic deletion and return immediately</td></tr>
+</table>
+</p>
+<p><pre>DeleteTopics Request (Version: 3) => [topics] timeout 
+  topics => STRING
+  timeout => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to be deleted.</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for a topic to be completely deleted on the controller node. Values <= 0 will trigger topic deletion and return immediately</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>DeleteTopics Response (Version: 0) => [topic_error_codes] 
+  topic_error_codes => topic error_code 
+    topic => STRING
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topic_error_codes</td><td>An array of per topic error codes.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>DeleteTopics Response (Version: 1) => throttle_time_ms [topic_error_codes] 
+  throttle_time_ms => INT32
+  topic_error_codes => topic error_code 
+    topic => STRING
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topic_error_codes</td><td>An array of per topic error codes.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>DeleteTopics Response (Version: 2) => throttle_time_ms [topic_error_codes] 
+  throttle_time_ms => INT32
+  topic_error_codes => topic error_code 
+    topic => STRING
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topic_error_codes</td><td>An array of per topic error codes.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>DeleteTopics Response (Version: 3) => throttle_time_ms [topic_error_codes] 
+  throttle_time_ms => INT32
+  topic_error_codes => topic error_code 
+    topic => STRING
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topic_error_codes</td><td>An array of per topic error codes.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_DeleteRecords">DeleteRecords API (Key: 21):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>DeleteRecords Request (Version: 0) => [topics] timeout 
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset 
+      partition => INT32
+      offset => INT64
+  timeout => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>The offset before which the messages will be deleted. -1 means high-watermark for the partition.</td></tr>
+<tr>
+<td>timeout</td><td>The maximum time to await a response in ms.</td></tr>
+</table>
+</p>
+<p><pre>DeleteRecords Request (Version: 1) => [topics] timeout 
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset 
+      partition => INT32
+      offset => INT64
+  timeout => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>The offset before which the messages will be deleted. -1 means high-watermark for the partition.</td></tr>
+<tr>
+<td>timeout</td><td>The maximum time to await a response in ms.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>DeleteRecords Response (Version: 0) => throttle_time_ms [topics] 
+  throttle_time_ms => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition low_watermark error_code 
+      partition => INT32
+      low_watermark => INT64
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>low_watermark</td><td>Smallest available offset of all live replicas</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>DeleteRecords Response (Version: 1) => throttle_time_ms [topics] 
+  throttle_time_ms => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition low_watermark error_code 
+      partition => INT32
+      low_watermark => INT64
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>low_watermark</td><td>Smallest available offset of all live replicas</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_InitProducerId">InitProducerId API (Key: 22):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>InitProducerId Request (Version: 0) => transactional_id transaction_timeout_ms 
+  transactional_id => NULLABLE_STRING
+  transaction_timeout_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id or null if the producer is not transactional</td></tr>
+<tr>
+<td>transaction_timeout_ms</td><td>The time in ms to wait for before aborting idle transactions sent by this producer.</td></tr>
+</table>
+</p>
+<p><pre>InitProducerId Request (Version: 1) => transactional_id transaction_timeout_ms 
+  transactional_id => NULLABLE_STRING
+  transaction_timeout_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id or null if the producer is not transactional</td></tr>
+<tr>
+<td>transaction_timeout_ms</td><td>The time in ms to wait for before aborting idle transactions sent by this producer.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>InitProducerId Response (Version: 0) => throttle_time_ms error_code producer_id producer_epoch 
+  throttle_time_ms => INT32
+  error_code => INT16
+  producer_id => INT64
+  producer_epoch => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+</table>
+</p>
+<p><pre>InitProducerId Response (Version: 1) => throttle_time_ms error_code producer_id producer_epoch 
+  throttle_time_ms => INT32
+  error_code => INT16
+  producer_id => INT64
+  producer_epoch => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_OffsetForLeaderEpoch">OffsetForLeaderEpoch API (Key: 23):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>OffsetForLeaderEpoch Request (Version: 0) => [topics] 
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition leader_epoch 
+      partition => INT32
+      leader_epoch => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to get epochs for</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>An array of partitions to get epochs for</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader_epoch</td><td>The epoch to lookup an offset for.</td></tr>
+</table>
+</p>
+<p><pre>OffsetForLeaderEpoch Request (Version: 1) => [topics] 
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition leader_epoch 
+      partition => INT32
+      leader_epoch => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to get epochs for</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>An array of partitions to get epochs for</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader_epoch</td><td>The epoch to lookup an offset for.</td></tr>
+</table>
+</p>
+<p><pre>OffsetForLeaderEpoch Request (Version: 2) => [topics] 
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition current_leader_epoch leader_epoch 
+      partition => INT32
+      current_leader_epoch => INT32
+      leader_epoch => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics to get epochs for</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>An array of partitions to get epochs for</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>current_leader_epoch</td><td>The current leader epoch, if provided, is used to fence consumers/replicas with old metadata. If the epoch provided by the client is larger than the current epoch known to the broker, then the UNKNOWN_LEADER_EPOCH error code will be returned. If the provided epoch is smaller, then the FENCED_LEADER_EPOCH error code will be returned.</td></tr>
+<tr>
+<td>leader_epoch</td><td>The epoch to lookup an offset for.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>OffsetForLeaderEpoch Response (Version: 0) => [topics] 
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => error_code partition end_offset 
+      error_code => INT16
+      partition => INT32
+      end_offset => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics for which we have leader offsets for some requested partition leader epoch</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>An array of offsets by partition</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>end_offset</td><td>The end offset</td></tr>
+</table>
+</p>
+<p><pre>OffsetForLeaderEpoch Response (Version: 1) => [topics] 
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => error_code partition leader_epoch end_offset 
+      error_code => INT16
+      partition => INT32
+      leader_epoch => INT32
+      end_offset => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>An array of topics for which we have leader offsets for some requested partition leader epoch</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>An array of offsets by partition</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch</td></tr>
+<tr>
+<td>end_offset</td><td>The end offset</td></tr>
+</table>
+</p>
+<p><pre>OffsetForLeaderEpoch Response (Version: 2) => throttle_time_ms [topics] 
+  throttle_time_ms => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => error_code partition leader_epoch end_offset 
+      error_code => INT16
+      partition => INT32
+      leader_epoch => INT32
+      end_offset => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topics</td><td>An array of topics for which we have leader offsets for some requested partition leader epoch</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>An array of offsets by partition</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch</td></tr>
+<tr>
+<td>end_offset</td><td>The end offset</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_AddPartitionsToTxn">AddPartitionsToTxn API (Key: 24):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>AddPartitionsToTxn Request (Version: 0) => transactional_id producer_id producer_epoch [topics] 
+  transactional_id => STRING
+  producer_id => INT64
+  producer_epoch => INT16
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id corresponding to the transaction.</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>topics</td><td>The partitions to add to the transaction.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>AddPartitionsToTxn Request (Version: 1) => transactional_id producer_id producer_epoch [topics] 
+  transactional_id => STRING
+  producer_id => INT64
+  producer_epoch => INT16
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id corresponding to the transaction.</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>topics</td><td>The partitions to add to the transaction.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>AddPartitionsToTxn Response (Version: 0) => throttle_time_ms [errors] 
+  throttle_time_ms => INT32
+  errors => topic [partition_errors] 
+    topic => STRING
+    partition_errors => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>errors</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_errors</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>AddPartitionsToTxn Response (Version: 1) => throttle_time_ms [errors] 
+  throttle_time_ms => INT32
+  errors => topic [partition_errors] 
+    topic => STRING
+    partition_errors => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>errors</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partition_errors</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_AddOffsetsToTxn">AddOffsetsToTxn API (Key: 25):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>AddOffsetsToTxn Request (Version: 0) => transactional_id producer_id producer_epoch group_id 
+  transactional_id => STRING
+  producer_id => INT64
+  producer_epoch => INT16
+  group_id => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id corresponding to the transaction.</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+</table>
+</p>
+<p><pre>AddOffsetsToTxn Request (Version: 1) => transactional_id producer_id producer_epoch group_id 
+  transactional_id => STRING
+  producer_id => INT64
+  producer_epoch => INT16
+  group_id => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id corresponding to the transaction.</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>AddOffsetsToTxn Response (Version: 0) => throttle_time_ms error_code 
+  throttle_time_ms => INT32
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>AddOffsetsToTxn Response (Version: 1) => throttle_time_ms error_code 
+  throttle_time_ms => INT32
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_EndTxn">EndTxn API (Key: 26):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>EndTxn Request (Version: 0) => transactional_id producer_id producer_epoch transaction_result 
+  transactional_id => STRING
+  producer_id => INT64
+  producer_epoch => INT16
+  transaction_result => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id corresponding to the transaction.</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>transaction_result</td><td>The result of the transaction (0 = ABORT, 1 = COMMIT)</td></tr>
+</table>
+</p>
+<p><pre>EndTxn Request (Version: 1) => transactional_id producer_id producer_epoch transaction_result 
+  transactional_id => STRING
+  producer_id => INT64
+  producer_epoch => INT16
+  transaction_result => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id corresponding to the transaction.</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>transaction_result</td><td>The result of the transaction (0 = ABORT, 1 = COMMIT)</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>EndTxn Response (Version: 0) => throttle_time_ms error_code 
+  throttle_time_ms => INT32
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>EndTxn Response (Version: 1) => throttle_time_ms error_code 
+  throttle_time_ms => INT32
+  error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_WriteTxnMarkers">WriteTxnMarkers API (Key: 27):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>WriteTxnMarkers Request (Version: 0) => [transaction_markers] 
+  transaction_markers => producer_id producer_epoch transaction_result [topics] coordinator_epoch 
+    producer_id => INT64
+    producer_epoch => INT16
+    transaction_result => BOOLEAN
+    topics => topic [partitions] 
+      topic => STRING
+      partitions => INT32
+    coordinator_epoch => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transaction_markers</td><td>The transaction markers to be written.</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>transaction_result</td><td>The result of the transaction to write to the partitions (false = ABORT, true = COMMIT).</td></tr>
+<tr>
+<td>topics</td><td>The partitions to write markers for.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>coordinator_epoch</td><td>Epoch associated with the transaction state partition hosted by this transaction coordinator</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>WriteTxnMarkers Response (Version: 0) => [transaction_markers] 
+  transaction_markers => producer_id [topics] 
+    producer_id => INT64
+    topics => topic [partitions] 
+      topic => STRING
+      partitions => partition error_code 
+        partition => INT32
+        error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transaction_markers</td><td>Errors per partition from writing markers.</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>topics</td><td>Errors per partition from writing markers.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_TxnOffsetCommit">TxnOffsetCommit API (Key: 28):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>TxnOffsetCommit Request (Version: 0) => transactional_id group_id producer_id producer_epoch [topics] 
+  transactional_id => STRING
+  group_id => STRING
+  producer_id => INT64
+  producer_epoch => INT16
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset metadata 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id corresponding to the transaction.</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<p><pre>TxnOffsetCommit Request (Version: 1) => transactional_id group_id producer_id producer_epoch [topics] 
+  transactional_id => STRING
+  group_id => STRING
+  producer_id => INT64
+  producer_epoch => INT16
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset metadata 
+      partition => INT32
+      offset => INT64
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id corresponding to the transaction.</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<p><pre>TxnOffsetCommit Request (Version: 2) => transactional_id group_id producer_id producer_epoch [topics] 
+  transactional_id => STRING
+  group_id => STRING
+  producer_id => INT64
+  producer_epoch => INT16
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition offset leader_epoch metadata 
+      partition => INT32
+      offset => INT64
+      leader_epoch => INT32
+      metadata => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>transactional_id</td><td>The transactional id corresponding to the transaction.</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>producer_id</td><td>Current producer id in use by the transactional id.</td></tr>
+<tr>
+<td>producer_epoch</td><td>Current epoch associated with the producer id.</td></tr>
+<tr>
+<td>topics</td><td>Topics to commit offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Partitions to commit offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>offset</td><td>Message offset to be committed</td></tr>
+<tr>
+<td>leader_epoch</td><td>The leader epoch, if provided is derived from the last consumed record. This is used by the consumer to check for log truncation and to ensure partition metadata is up to date following a group rebalance.</td></tr>
+<tr>
+<td>metadata</td><td>Any associated metadata the client wants to keep.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>TxnOffsetCommit Response (Version: 0) => throttle_time_ms [topics] 
+  throttle_time_ms => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topics</td><td>Responses by topic for committed offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Responses by partition for committed offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>TxnOffsetCommit Response (Version: 1) => throttle_time_ms [topics] 
+  throttle_time_ms => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topics</td><td>Responses by topic for committed offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Responses by partition for committed offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>TxnOffsetCommit Response (Version: 2) => throttle_time_ms [topics] 
+  throttle_time_ms => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topics</td><td>Responses by topic for committed offsets</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>Responses by partition for committed offsets</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_DescribeAcls">DescribeAcls API (Key: 29):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>DescribeAcls Request (Version: 0) => resource_type resource_name principal host operation permission_type 
+  resource_type => INT8
+  resource_name => NULLABLE_STRING
+  principal => NULLABLE_STRING
+  host => NULLABLE_STRING
+  operation => INT8
+  permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name filter</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal filter</td></tr>
+<tr>
+<td>host</td><td>The ACL host filter</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<p><pre>DescribeAcls Request (Version: 1) => resource_type resource_name resource_pattern_type_filter principal host operation permission_type 
+  resource_type => INT8
+  resource_name => NULLABLE_STRING
+  resource_pattern_type_filter => INT8
+  principal => NULLABLE_STRING
+  host => NULLABLE_STRING
+  operation => INT8
+  permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name filter</td></tr>
+<tr>
+<td>resource_pattern_type_filter</td><td>The resource pattern type filter</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal filter</td></tr>
+<tr>
+<td>host</td><td>The ACL host filter</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>DescribeAcls Response (Version: 0) => throttle_time_ms error_code error_message [resources] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  error_message => NULLABLE_STRING
+  resources => resource_type resource_name [acls] 
+    resource_type => INT8
+    resource_name => STRING
+    acls => principal host operation permission_type 
+      principal => STRING
+      host => STRING
+      operation => INT8
+      permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>resources</td><td>The resources and their associated ACLs.</td></tr>
+<tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name</td></tr>
+<tr>
+<td>acls</td><td>null</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal</td></tr>
+<tr>
+<td>host</td><td>The ACL host</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<p><pre>DescribeAcls Response (Version: 1) => throttle_time_ms error_code error_message [resources] 
+  throttle_time_ms => INT32
+  error_code => INT16
+  error_message => NULLABLE_STRING
+  resources => resource_type resource_name resource_pattten_type [acls] 
+    resource_type => INT8
+    resource_name => STRING
+    resource_pattten_type => INT8
+    acls => principal host operation permission_type 
+      principal => STRING
+      host => STRING
+      operation => INT8
+      permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>resources</td><td>The resources and their associated ACLs.</td></tr>
+<tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name</td></tr>
+<tr>
+<td>resource_pattten_type</td><td>The resource pattern type</td></tr>
+<tr>
+<td>acls</td><td>null</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal</td></tr>
+<tr>
+<td>host</td><td>The ACL host</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_CreateAcls">CreateAcls API (Key: 30):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>CreateAcls Request (Version: 0) => [creations] 
+  creations => resource_type resource_name principal host operation permission_type 
+    resource_type => INT8
+    resource_name => STRING
+    principal => STRING
+    host => STRING
+    operation => INT8
+    permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>creations</td><td>null</td></tr>
+<tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal</td></tr>
+<tr>
+<td>host</td><td>The ACL host</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<p><pre>CreateAcls Request (Version: 1) => [creations] 
+  creations => resource_type resource_name resource_pattten_type principal host operation permission_type 
+    resource_type => INT8
+    resource_name => STRING
+    resource_pattten_type => INT8
+    principal => STRING
+    host => STRING
+    operation => INT8
+    permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>creations</td><td>null</td></tr>
+<tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name</td></tr>
+<tr>
+<td>resource_pattten_type</td><td>The resource pattern type</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal</td></tr>
+<tr>
+<td>host</td><td>The ACL host</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>CreateAcls Response (Version: 0) => throttle_time_ms [creation_responses] 
+  throttle_time_ms => INT32
+  creation_responses => error_code error_message 
+    error_code => INT16
+    error_message => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>creation_responses</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+</table>
+</p>
+<p><pre>CreateAcls Response (Version: 1) => throttle_time_ms [creation_responses] 
+  throttle_time_ms => INT32
+  creation_responses => error_code error_message 
+    error_code => INT16
+    error_message => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>creation_responses</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_DeleteAcls">DeleteAcls API (Key: 31):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>DeleteAcls Request (Version: 0) => [filters] 
+  filters => resource_type resource_name principal host operation permission_type 
+    resource_type => INT8
+    resource_name => NULLABLE_STRING
+    principal => NULLABLE_STRING
+    host => NULLABLE_STRING
+    operation => INT8
+    permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>filters</td><td>null</td></tr>
+<tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name filter</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal filter</td></tr>
+<tr>
+<td>host</td><td>The ACL host filter</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<p><pre>DeleteAcls Request (Version: 1) => [filters] 
+  filters => resource_type resource_name resource_pattern_type_filter principal host operation permission_type 
+    resource_type => INT8
+    resource_name => NULLABLE_STRING
+    resource_pattern_type_filter => INT8
+    principal => NULLABLE_STRING
+    host => NULLABLE_STRING
+    operation => INT8
+    permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>filters</td><td>null</td></tr>
+<tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name filter</td></tr>
+<tr>
+<td>resource_pattern_type_filter</td><td>The resource pattern type filter</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal filter</td></tr>
+<tr>
+<td>host</td><td>The ACL host filter</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>DeleteAcls Response (Version: 0) => throttle_time_ms [filter_responses] 
+  throttle_time_ms => INT32
+  filter_responses => error_code error_message [matching_acls] 
+    error_code => INT16
+    error_message => NULLABLE_STRING
+    matching_acls => error_code error_message resource_type resource_name principal host operation permission_type 
+      error_code => INT16
+      error_message => NULLABLE_STRING
+      resource_type => INT8
+      resource_name => STRING
+      principal => STRING
+      host => STRING
+      operation => INT8
+      permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>filter_responses</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>matching_acls</td><td>The matching ACLs</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal</td></tr>
+<tr>
+<td>host</td><td>The ACL host</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<p><pre>DeleteAcls Response (Version: 1) => throttle_time_ms [filter_responses] 
+  throttle_time_ms => INT32
+  filter_responses => error_code error_message [matching_acls] 
+    error_code => INT16
+    error_message => NULLABLE_STRING
+    matching_acls => error_code error_message resource_type resource_name resource_pattten_type principal host operation permission_type 
+      error_code => INT16
+      error_message => NULLABLE_STRING
+      resource_type => INT8
+      resource_name => STRING
+      resource_pattten_type => INT8
+      principal => STRING
+      host => STRING
+      operation => INT8
+      permission_type => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>filter_responses</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>matching_acls</td><td>The matching ACLs</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>resource_type</td><td>The resource type</td></tr>
+<tr>
+<td>resource_name</td><td>The resource name</td></tr>
+<tr>
+<td>resource_pattten_type</td><td>The resource pattern type</td></tr>
+<tr>
+<td>principal</td><td>The ACL principal</td></tr>
+<tr>
+<td>host</td><td>The ACL host</td></tr>
+<tr>
+<td>operation</td><td>The ACL operation</td></tr>
+<tr>
+<td>permission_type</td><td>The ACL permission type</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_DescribeConfigs">DescribeConfigs API (Key: 32):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>DescribeConfigs Request (Version: 0) => [resources] 
+  resources => resource_type resource_name [config_names] 
+    resource_type => INT8
+    resource_name => STRING
+    config_names => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>resources</td><td>An array of config resources to be returned.</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+<tr>
+<td>config_names</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>DescribeConfigs Request (Version: 1) => [resources] include_synonyms 
+  resources => resource_type resource_name [config_names] 
+    resource_type => INT8
+    resource_name => STRING
+    config_names => STRING
+  include_synonyms => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>resources</td><td>An array of config resources to be returned.</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+<tr>
+<td>config_names</td><td>null</td></tr>
+<tr>
+<td>include_synonyms</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>DescribeConfigs Request (Version: 2) => [resources] include_synonyms 
+  resources => resource_type resource_name [config_names] 
+    resource_type => INT8
+    resource_name => STRING
+    config_names => STRING
+  include_synonyms => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>resources</td><td>An array of config resources to be returned.</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+<tr>
+<td>config_names</td><td>null</td></tr>
+<tr>
+<td>include_synonyms</td><td>null</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>DescribeConfigs Response (Version: 0) => throttle_time_ms [resources] 
+  throttle_time_ms => INT32
+  resources => error_code error_message resource_type resource_name [config_entries] 
+    error_code => INT16
+    error_message => NULLABLE_STRING
+    resource_type => INT8
+    resource_name => STRING
+    config_entries => config_name config_value read_only is_default is_sensitive 
+      config_name => STRING
+      config_value => NULLABLE_STRING
+      read_only => BOOLEAN
+      is_default => BOOLEAN
+      is_sensitive => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>resources</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+<tr>
+<td>config_entries</td><td>null</td></tr>
+<tr>
+<td>config_name</td><td>null</td></tr>
+<tr>
+<td>config_value</td><td>null</td></tr>
+<tr>
+<td>read_only</td><td>null</td></tr>
+<tr>
+<td>is_default</td><td>null</td></tr>
+<tr>
+<td>is_sensitive</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>DescribeConfigs Response (Version: 1) => throttle_time_ms [resources] 
+  throttle_time_ms => INT32
+  resources => error_code error_message resource_type resource_name [config_entries] 
+    error_code => INT16
+    error_message => NULLABLE_STRING
+    resource_type => INT8
+    resource_name => STRING
+    config_entries => config_name config_value read_only config_source is_sensitive [config_synonyms] 
+      config_name => STRING
+      config_value => NULLABLE_STRING
+      read_only => BOOLEAN
+      config_source => INT8
+      is_sensitive => BOOLEAN
+      config_synonyms => config_name config_value config_source 
+        config_name => STRING
+        config_value => NULLABLE_STRING
+        config_source => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>resources</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+<tr>
+<td>config_entries</td><td>null</td></tr>
+<tr>
+<td>config_name</td><td>null</td></tr>
+<tr>
+<td>config_value</td><td>null</td></tr>
+<tr>
+<td>read_only</td><td>null</td></tr>
+<tr>
+<td>config_source</td><td>null</td></tr>
+<tr>
+<td>is_sensitive</td><td>null</td></tr>
+<tr>
+<td>config_synonyms</td><td>null</td></tr>
+<tr>
+<td>config_name</td><td>null</td></tr>
+<tr>
+<td>config_value</td><td>null</td></tr>
+<tr>
+<td>config_source</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>DescribeConfigs Response (Version: 2) => throttle_time_ms [resources] 
+  throttle_time_ms => INT32
+  resources => error_code error_message resource_type resource_name [config_entries] 
+    error_code => INT16
+    error_message => NULLABLE_STRING
+    resource_type => INT8
+    resource_name => STRING
+    config_entries => config_name config_value read_only config_source is_sensitive [config_synonyms] 
+      config_name => STRING
+      config_value => NULLABLE_STRING
+      read_only => BOOLEAN
+      config_source => INT8
+      is_sensitive => BOOLEAN
+      config_synonyms => config_name config_value config_source 
+        config_name => STRING
+        config_value => NULLABLE_STRING
+        config_source => INT8
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>resources</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+<tr>
+<td>config_entries</td><td>null</td></tr>
+<tr>
+<td>config_name</td><td>null</td></tr>
+<tr>
+<td>config_value</td><td>null</td></tr>
+<tr>
+<td>read_only</td><td>null</td></tr>
+<tr>
+<td>config_source</td><td>null</td></tr>
+<tr>
+<td>is_sensitive</td><td>null</td></tr>
+<tr>
+<td>config_synonyms</td><td>null</td></tr>
+<tr>
+<td>config_name</td><td>null</td></tr>
+<tr>
+<td>config_value</td><td>null</td></tr>
+<tr>
+<td>config_source</td><td>null</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_AlterConfigs">AlterConfigs API (Key: 33):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>AlterConfigs Request (Version: 0) => [resources] validate_only 
+  resources => resource_type resource_name [config_entries] 
+    resource_type => INT8
+    resource_name => STRING
+    config_entries => config_name config_value 
+      config_name => STRING
+      config_value => NULLABLE_STRING
+  validate_only => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>resources</td><td>An array of resources to update with the provided configs.</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+<tr>
+<td>config_entries</td><td>null</td></tr>
+<tr>
+<td>config_name</td><td>Configuration name</td></tr>
+<tr>
+<td>config_value</td><td>Configuration value</td></tr>
+<tr>
+<td>validate_only</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>AlterConfigs Request (Version: 1) => [resources] validate_only 
+  resources => resource_type resource_name [config_entries] 
+    resource_type => INT8
+    resource_name => STRING
+    config_entries => config_name config_value 
+      config_name => STRING
+      config_value => NULLABLE_STRING
+  validate_only => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>resources</td><td>An array of resources to update with the provided configs.</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+<tr>
+<td>config_entries</td><td>null</td></tr>
+<tr>
+<td>config_name</td><td>Configuration name</td></tr>
+<tr>
+<td>config_value</td><td>Configuration value</td></tr>
+<tr>
+<td>validate_only</td><td>null</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>AlterConfigs Response (Version: 0) => throttle_time_ms [resources] 
+  throttle_time_ms => INT32
+  resources => error_code error_message resource_type resource_name 
+    error_code => INT16
+    error_message => NULLABLE_STRING
+    resource_type => INT8
+    resource_name => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>resources</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+</table>
+</p>
+<p><pre>AlterConfigs Response (Version: 1) => throttle_time_ms [resources] 
+  throttle_time_ms => INT32
+  resources => error_code error_message resource_type resource_name 
+    error_code => INT16
+    error_message => NULLABLE_STRING
+    resource_type => INT8
+    resource_name => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>resources</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>resource_type</td><td>null</td></tr>
+<tr>
+<td>resource_name</td><td>null</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_AlterReplicaLogDirs">AlterReplicaLogDirs API (Key: 34):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>AlterReplicaLogDirs Request (Version: 0) => [log_dirs] 
+  log_dirs => log_dir [topics] 
+    log_dir => STRING
+    topics => topic [partitions] 
+      topic => STRING
+      partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>log_dirs</td><td>null</td></tr>
+<tr>
+<td>log_dir</td><td>The absolute log directory path.</td></tr>
+<tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>List of partition ids of the topic.</td></tr>
+</table>
+</p>
+<p><pre>AlterReplicaLogDirs Request (Version: 1) => [log_dirs] 
+  log_dirs => log_dir [topics] 
+    log_dir => STRING
+    topics => topic [partitions] 
+      topic => STRING
+      partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>log_dirs</td><td>null</td></tr>
+<tr>
+<td>log_dir</td><td>The absolute log directory path.</td></tr>
+<tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>List of partition ids of the topic.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>AlterReplicaLogDirs Response (Version: 0) => throttle_time_ms [topics] 
+  throttle_time_ms => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>AlterReplicaLogDirs Response (Version: 1) => throttle_time_ms [topics] 
+  throttle_time_ms => INT32
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => partition error_code 
+      partition => INT32
+      error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_DescribeLogDirs">DescribeLogDirs API (Key: 35):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>DescribeLogDirs Request (Version: 0) => [topics] 
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>List of partition ids of the topic.</td></tr>
+</table>
+</p>
+<p><pre>DescribeLogDirs Request (Version: 1) => [topics] 
+  topics => topic [partitions] 
+    topic => STRING
+    partitions => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>List of partition ids of the topic.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>DescribeLogDirs Response (Version: 0) => throttle_time_ms [log_dirs] 
+  throttle_time_ms => INT32
+  log_dirs => error_code log_dir [topics] 
+    error_code => INT16
+    log_dir => STRING
+    topics => topic [partitions] 
+      topic => STRING
+      partitions => partition size offset_lag is_future 
+        partition => INT32
+        size => INT64
+        offset_lag => INT64
+        is_future => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>log_dirs</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>log_dir</td><td>The absolute log directory path.</td></tr>
+<tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>size</td><td>The size of the log segments of the partition in bytes.</td></tr>
+<tr>
+<td>offset_lag</td><td>The lag of the log's LEO w.r.t. partition's HW (if it is the current log for the partition) or current replica's LEO (if it is the future log for the partition)</td></tr>
+<tr>
+<td>is_future</td><td>True if this log is created by AlterReplicaLogDirsRequest and will replace the current log of the replica in the future.</td></tr>
+</table>
+</p>
+<p><pre>DescribeLogDirs Response (Version: 1) => throttle_time_ms [log_dirs] 
+  throttle_time_ms => INT32
+  log_dirs => error_code log_dir [topics] 
+    error_code => INT16
+    log_dir => STRING
+    topics => topic [partitions] 
+      topic => STRING
+      partitions => partition size offset_lag is_future 
+        partition => INT32
+        size => INT64
+        offset_lag => INT64
+        is_future => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>log_dirs</td><td>null</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>log_dir</td><td>The absolute log directory path.</td></tr>
+<tr>
+<td>topics</td><td>null</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>partitions</td><td>null</td></tr>
+<tr>
+<td>partition</td><td>Topic partition id</td></tr>
+<tr>
+<td>size</td><td>The size of the log segments of the partition in bytes.</td></tr>
+<tr>
+<td>offset_lag</td><td>The lag of the log's LEO w.r.t. partition's HW (if it is the current log for the partition) or current replica's LEO (if it is the future log for the partition)</td></tr>
+<tr>
+<td>is_future</td><td>True if this log is created by AlterReplicaLogDirsRequest and will replace the current log of the replica in the future.</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_SaslAuthenticate">SaslAuthenticate API (Key: 36):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>SaslAuthenticate Request (Version: 0) => sasl_auth_bytes 
+  sasl_auth_bytes => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>sasl_auth_bytes</td><td>SASL authentication bytes from client as defined by the SASL mechanism.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>SaslAuthenticate Response (Version: 0) => error_code error_message sasl_auth_bytes 
+  error_code => INT16
+  error_message => NULLABLE_STRING
+  sasl_auth_bytes => BYTES
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+<tr>
+<td>sasl_auth_bytes</td><td>SASL authentication bytes from server as defined by the SASL mechanism.</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_CreatePartitions">CreatePartitions API (Key: 37):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>CreatePartitions Request (Version: 0) => [topic_partitions] timeout validate_only 
+  topic_partitions => topic new_partitions 
+    topic => STRING
+    new_partitions => count [assignment] 
+      count => INT32
+      assignment => ARRAY(INT32)
+  timeout => INT32
+  validate_only => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topic_partitions</td><td>List of topic and the corresponding new partitions.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>new_partitions</td><td>null</td></tr>
+<tr>
+<td>count</td><td>The new partition count.</td></tr>
+<tr>
+<td>assignment</td><td>The assigned brokers.</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for the partitions to be created.</td></tr>
+<tr>
+<td>validate_only</td><td>If true then validate the request, but don't actually increase the number of partitions.</td></tr>
+</table>
+</p>
+<p><pre>CreatePartitions Request (Version: 1) => [topic_partitions] timeout validate_only 
+  topic_partitions => topic new_partitions 
+    topic => STRING
+    new_partitions => count [assignment] 
+      count => INT32
+      assignment => ARRAY(INT32)
+  timeout => INT32
+  validate_only => BOOLEAN
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>topic_partitions</td><td>List of topic and the corresponding new partitions.</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>new_partitions</td><td>null</td></tr>
+<tr>
+<td>count</td><td>The new partition count.</td></tr>
+<tr>
+<td>assignment</td><td>The assigned brokers.</td></tr>
+<tr>
+<td>timeout</td><td>The time in ms to wait for the partitions to be created.</td></tr>
+<tr>
+<td>validate_only</td><td>If true then validate the request, but don't actually increase the number of partitions.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>CreatePartitions Response (Version: 0) => throttle_time_ms [topic_errors] 
+  throttle_time_ms => INT32
+  topic_errors => topic error_code error_message 
+    topic => STRING
+    error_code => INT16
+    error_message => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topic_errors</td><td>Per topic results for the create partitions request</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+</table>
+</p>
+<p><pre>CreatePartitions Response (Version: 1) => throttle_time_ms [topic_errors] 
+  throttle_time_ms => INT32
+  topic_errors => topic error_code error_message 
+    topic => STRING
+    error_code => INT16
+    error_message => NULLABLE_STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>topic_errors</td><td>Per topic results for the create partitions request</td></tr>
+<tr>
+<td>topic</td><td>Name of topic</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>error_message</td><td>Response error message</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_CreateDelegationToken">CreateDelegationToken API (Key: 38):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>CreateDelegationToken Request (Version: 0) => [renewers] max_life_time 
+  renewers => principal_type name 
+    principal_type => STRING
+    name => STRING
+  max_life_time => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>renewers</td><td>An array of token renewers. Renewer is an Kafka PrincipalType and name string, who is allowed to renew this token before the max lifetime expires.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+<tr>
+<td>max_life_time</td><td>Max lifetime period for token in milli seconds. if value is -1, then max lifetime  will default to a server side config value.</td></tr>
+</table>
+</p>
+<p><pre>CreateDelegationToken Request (Version: 1) => [renewers] max_life_time 
+  renewers => principal_type name 
+    principal_type => STRING
+    name => STRING
+  max_life_time => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>renewers</td><td>An array of token renewers. Renewer is an Kafka PrincipalType and name string, who is allowed to renew this token before the max lifetime expires.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+<tr>
+<td>max_life_time</td><td>Max lifetime period for token in milli seconds. if value is -1, then max lifetime  will default to a server side config value.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>CreateDelegationToken Response (Version: 0) => error_code owner issue_timestamp expiry_timestamp max_timestamp token_id hmac throttle_time_ms 
+  error_code => INT16
+  owner => principal_type name 
+    principal_type => STRING
+    name => STRING
+  issue_timestamp => INT64
+  expiry_timestamp => INT64
+  max_timestamp => INT64
+  token_id => STRING
+  hmac => BYTES
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>owner</td><td>token owner.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+<tr>
+<td>issue_timestamp</td><td>timestamp (in msec) when this token was generated.</td></tr>
+<tr>
+<td>expiry_timestamp</td><td>timestamp (in msec) at which this token expires.</td></tr>
+<tr>
+<td>max_timestamp</td><td>max life time of this token.</td></tr>
+<tr>
+<td>token_id</td><td>UUID to ensure uniqueness.</td></tr>
+<tr>
+<td>hmac</td><td>HMAC of the delegation token.</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>CreateDelegationToken Response (Version: 1) => error_code owner issue_timestamp expiry_timestamp max_timestamp token_id hmac throttle_time_ms 
+  error_code => INT16
+  owner => principal_type name 
+    principal_type => STRING
+    name => STRING
+  issue_timestamp => INT64
+  expiry_timestamp => INT64
+  max_timestamp => INT64
+  token_id => STRING
+  hmac => BYTES
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>owner</td><td>token owner.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+<tr>
+<td>issue_timestamp</td><td>timestamp (in msec) when this token was generated.</td></tr>
+<tr>
+<td>expiry_timestamp</td><td>timestamp (in msec) at which this token expires.</td></tr>
+<tr>
+<td>max_timestamp</td><td>max life time of this token.</td></tr>
+<tr>
+<td>token_id</td><td>UUID to ensure uniqueness.</td></tr>
+<tr>
+<td>hmac</td><td>HMAC of the delegation token.</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_RenewDelegationToken">RenewDelegationToken API (Key: 39):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>RenewDelegationToken Request (Version: 0) => hmac renew_time_period 
+  hmac => BYTES
+  renew_time_period => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>hmac</td><td>HMAC of the delegation token to be renewed.</td></tr>
+<tr>
+<td>renew_time_period</td><td>Renew time period in milli seconds.</td></tr>
+</table>
+</p>
+<p><pre>RenewDelegationToken Request (Version: 1) => hmac renew_time_period 
+  hmac => BYTES
+  renew_time_period => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>hmac</td><td>HMAC of the delegation token to be renewed.</td></tr>
+<tr>
+<td>renew_time_period</td><td>Renew time period in milli seconds.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>RenewDelegationToken Response (Version: 0) => error_code expiry_timestamp throttle_time_ms 
+  error_code => INT16
+  expiry_timestamp => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>expiry_timestamp</td><td>timestamp (in msec) at which this token expires..</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>RenewDelegationToken Response (Version: 1) => error_code expiry_timestamp throttle_time_ms 
+  error_code => INT16
+  expiry_timestamp => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>expiry_timestamp</td><td>timestamp (in msec) at which this token expires..</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_ExpireDelegationToken">ExpireDelegationToken API (Key: 40):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>ExpireDelegationToken Request (Version: 0) => hmac expiry_time_period 
+  hmac => BYTES
+  expiry_time_period => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>hmac</td><td>HMAC of the delegation token to be expired.</td></tr>
+<tr>
+<td>expiry_time_period</td><td>expiry time period in milli seconds.</td></tr>
+</table>
+</p>
+<p><pre>ExpireDelegationToken Request (Version: 1) => hmac expiry_time_period 
+  hmac => BYTES
+  expiry_time_period => INT64
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>hmac</td><td>HMAC of the delegation token to be expired.</td></tr>
+<tr>
+<td>expiry_time_period</td><td>expiry time period in milli seconds.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>ExpireDelegationToken Response (Version: 0) => error_code expiry_timestamp throttle_time_ms 
+  error_code => INT16
+  expiry_timestamp => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>expiry_timestamp</td><td>timestamp (in msec) at which this token expires..</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>ExpireDelegationToken Response (Version: 1) => error_code expiry_timestamp throttle_time_ms 
+  error_code => INT16
+  expiry_timestamp => INT64
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>expiry_timestamp</td><td>timestamp (in msec) at which this token expires..</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_DescribeDelegationToken">DescribeDelegationToken API (Key: 41):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>DescribeDelegationToken Request (Version: 0) => [owners] 
+  owners => principal_type name 
+    principal_type => STRING
+    name => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>owners</td><td>An array of token owners.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+</table>
+</p>
+<p><pre>DescribeDelegationToken Request (Version: 1) => [owners] 
+  owners => principal_type name 
+    principal_type => STRING
+    name => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>owners</td><td>An array of token owners.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>DescribeDelegationToken Response (Version: 0) => error_code [token_details] throttle_time_ms 
+  error_code => INT16
+  token_details => owner issue_timestamp expiry_timestamp max_timestamp token_id hmac [renewers] 
+    owner => principal_type name 
+      principal_type => STRING
+      name => STRING
+    issue_timestamp => INT64
+    expiry_timestamp => INT64
+    max_timestamp => INT64
+    token_id => STRING
+    hmac => BYTES
+    renewers => principal_type name 
+      principal_type => STRING
+      name => STRING
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>token_details</td><td>null</td></tr>
+<tr>
+<td>owner</td><td>token owner.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+<tr>
+<td>issue_timestamp</td><td>timestamp (in msec) when this token was generated.</td></tr>
+<tr>
+<td>expiry_timestamp</td><td>timestamp (in msec) at which this token expires.</td></tr>
+<tr>
+<td>max_timestamp</td><td>max life time of this token.</td></tr>
+<tr>
+<td>token_id</td><td>UUID to ensure uniqueness.</td></tr>
+<tr>
+<td>hmac</td><td>HMAC of the delegation token to be expired.</td></tr>
+<tr>
+<td>renewers</td><td>An array of token renewers. Renewer is an Kafka PrincipalType and name string, who is allowed to renew this token before the max lifetime expires.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<p><pre>DescribeDelegationToken Response (Version: 1) => error_code [token_details] throttle_time_ms 
+  error_code => INT16
+  token_details => owner issue_timestamp expiry_timestamp max_timestamp token_id hmac [renewers] 
+    owner => principal_type name 
+      principal_type => STRING
+      name => STRING
+    issue_timestamp => INT64
+    expiry_timestamp => INT64
+    max_timestamp => INT64
+    token_id => STRING
+    hmac => BYTES
+    renewers => principal_type name 
+      principal_type => STRING
+      name => STRING
+  throttle_time_ms => INT32
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>error_code</td><td>Response error code</td></tr>
+<tr>
+<td>token_details</td><td>null</td></tr>
+<tr>
+<td>owner</td><td>token owner.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+<tr>
+<td>issue_timestamp</td><td>timestamp (in msec) when this token was generated.</td></tr>
+<tr>
+<td>expiry_timestamp</td><td>timestamp (in msec) at which this token expires.</td></tr>
+<tr>
+<td>max_timestamp</td><td>max life time of this token.</td></tr>
+<tr>
+<td>token_id</td><td>UUID to ensure uniqueness.</td></tr>
+<tr>
+<td>hmac</td><td>HMAC of the delegation token to be expired.</td></tr>
+<tr>
+<td>renewers</td><td>An array of token renewers. Renewer is an Kafka PrincipalType and name string, who is allowed to renew this token before the max lifetime expires.</td></tr>
+<tr>
+<td>principal_type</td><td>principalType of the Kafka principal</td></tr>
+<tr>
+<td>name</td><td>name of the Kafka principal</td></tr>
+<tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+</table>
+</p>
+<h5><a name="The_Messages_DeleteGroups">DeleteGroups API (Key: 42):</a></h5>
+
+<b>Requests:</b><br>
+<p><pre>DeleteGroups Request (Version: 0) => [groups] 
+  groups => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>groups</td><td>An array of groups to be deleted.</td></tr>
+</table>
+</p>
+<p><pre>DeleteGroups Request (Version: 1) => [groups] 
+  groups => STRING
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>groups</td><td>An array of groups to be deleted.</td></tr>
+</table>
+</p>
+<b>Responses:</b><br>
+<p><pre>DeleteGroups Response (Version: 0) => throttle_time_ms [group_error_codes] 
+  throttle_time_ms => INT32
+  group_error_codes => group_id error_code 
+    group_id => STRING
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>group_error_codes</td><td>An array of per group error codes.</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+<p><pre>DeleteGroups Response (Version: 1) => throttle_time_ms [group_error_codes] 
+  throttle_time_ms => INT32
+  group_error_codes => group_id error_code 
+    group_id => STRING
+    error_code => INT16
+</pre><table class="data-table"><tbody>
+<tr><th>Field</th>
+<th>Description</th>
+</tr><tr>
+<td>throttle_time_ms</td><td>Duration in milliseconds for which the request was throttled due to quota violation (Zero if the request did not violate any quota)</td></tr>
+<tr>
+<td>group_error_codes</td><td>An array of per group error codes.</td></tr>
+<tr>
+<td>group_id</td><td>The unique group identifier</td></tr>
+<tr>
+<td>error_code</td><td>Response error code</td></tr>
+</table>
+</p>
+
diff --git a/21/generated/protocol_types.html b/21/generated/protocol_types.html
index e69de29..5b34cb9 100644
--- a/21/generated/protocol_types.html
+++ b/21/generated/protocol_types.html
@@ -0,0 +1,20 @@
+<table class="data-table"><tbody>
+<tr><th>Type</th>
+<th>Description</th>
+</tr>
+<tr><td>BOOLEAN</td><td>Represents a boolean value in a byte. Values 0 and 1 are used to represent false and true respectively. When reading a boolean value, any non-zero value is considered true.</td></tr>
+<tr><td>INT8</td><td>Represents an integer between -2<sup>7</sup> and 2<sup>7</sup>-1 inclusive.</td></tr>
+<tr><td>INT16</td><td>Represents an integer between -2<sup>15</sup> and 2<sup>15</sup>-1 inclusive. The values are encoded using two bytes in network byte order (big-endian).</td></tr>
+<tr><td>INT32</td><td>Represents an integer between -2<sup>31</sup> and 2<sup>31</sup>-1 inclusive. The values are encoded using four bytes in network byte order (big-endian).</td></tr>
+<tr><td>INT64</td><td>Represents an integer between -2<sup>63</sup> and 2<sup>63</sup>-1 inclusive. The values are encoded using eight bytes in network byte order (big-endian).</td></tr>
+<tr><td>UINT32</td><td>Represents an integer between 0 and 2<sup>32</sup>-1 inclusive. The values are encoded using four bytes in network byte order (big-endian).</td></tr>
+<tr><td>VARINT</td><td>Represents an integer between -2<sup>31</sup> and 2<sup>31</sup>-1 inclusive. Encoding follows the variable-length zig-zag encoding from  <a href="http://code.google.com/apis/protocolbuffers/docs/encoding.html"> Google Protocol Buffers</a>.</td></tr>
+<tr><td>VARLONG</td><td>Represents an integer between -2<sup>63</sup> and 2<sup>63</sup>-1 inclusive. Encoding follows the variable-length zig-zag encoding from  <a href="http://code.google.com/apis/protocolbuffers/docs/encoding.html"> Google Protocol Buffers</a>.</td></tr>
+<tr><td>STRING</td><td>Represents a sequence of characters. First the length N is given as an INT16. Then N bytes follow which are the UTF-8 encoding of the character sequence. Length must not be negative.</td></tr>
+<tr><td>NULLABLE_STRING</td><td>Represents a sequence of characters or null. For non-null strings, first the length N is given as an INT16. Then N bytes follow which are the UTF-8 encoding of the character sequence. A null value is encoded with length of -1 and there are no following bytes.</td></tr>
+<tr><td>BYTES</td><td>Represents a raw sequence of bytes. First the length N is given as an INT32. Then N bytes follow.</td></tr>
+<tr><td>NULLABLE_BYTES</td><td>Represents a raw sequence of bytes or null. For non-null values, first the length N is given as an INT32. Then N bytes follow. A null value is encoded with length of -1 and there are no following bytes.</td></tr>
+<tr><td>RECORDS</td><td>Represents a sequence of Kafka records as NULLABLE_BYTES. For a detailed description of records see <a href="/documentation/#messageformat">Message Sets</a>.</td></tr>
+<tr><td>ARRAY</td><td>Represents a sequence of objects of a given type T. Type T can be either a primitive type (e.g. STRING) or a structure. First, the length N is given as an INT32. Then N instances of type T follow. A null array is represented with a length of -1. In protocol documentation an array of T instances is referred to as [T].</td></tr>
+</table>
+
diff --git a/21/generated/sink_connector_config.html b/21/generated/sink_connector_config.html
index e69de29..b14636e 100644
--- a/21/generated/sink_connector_config.html
+++ b/21/generated/sink_connector_config.html
@@ -0,0 +1,46 @@
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>name</td></td><td>Globally unique name to use for this connector.</td></td><td>string</td></td><td></td></td><td>non-empty string without ISO control characters</td></td><td>high</td></td></tr>
+<tr>
+<td>connector.class</td></td><td>Name or alias of the class for this connector. Must be a subclass of org.apache.kafka.connect.connector.Connector. If the connector is org.apache.kafka.connect.file.FileStreamSinkConnector, you can either specify this full name,  or use "FileStreamSink" or "FileStreamSinkConnector" to make the configuration a bit shorter</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>tasks.max</td></td><td>Maximum number of tasks to use for this connector.</td></td><td>int</td></td><td>1</td></td><td>[1,...]</td></td><td>high</td></td></tr>
+<tr>
+<td>topics</td></td><td>List of topics to consume, separated by commas</td></td><td>list</td></td><td>""</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>topics.regex</td></td><td>Regular expression giving topics to consume. Under the hood, the regex is compiled to a <code>java.util.regex.Pattern</code>. Only one of topics or topics.regex should be specified.</td></td><td>string</td></td><td>""</td></td><td>valid regex</td></td><td>high</td></td></tr>
+<tr>
+<td>key.converter</td></td><td>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>value.converter</td></td><td>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>header.converter</td></td><td>HeaderConverter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the header values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro. By default, the SimpleHeaderConverter is used to serialize header values to strings and deseria [...]
+<tr>
+<td>config.action.reload</td></td><td>The action that Connect should take on the connector when changes in external configuration providers result in a change in the connector's configuration properties. A value of 'none' indicates that Connect will do nothing. A value of 'restart' indicates that Connect should restart/reload the connector with the updated configuration properties.The restart may actually be scheduled in the future if the external configuration provider indicates that a  [...]
+<tr>
+<td>transforms</td></td><td>Aliases for the transformations to be applied to records.</td></td><td>list</td></td><td>""</td></td><td>non-null string, unique transformation aliases</td></td><td>low</td></td></tr>
+<tr>
+<td>errors.retry.timeout</td></td><td>The maximum duration in milliseconds that a failed operation will be reattempted. The default is 0, which means no retries will be attempted. Use -1 for infinite retries.</td></td><td>long</td></td><td>0</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.retry.delay.max.ms</td></td><td>The maximum duration in milliseconds between consecutive retry attempts. Jitter will be added to the delay once this limit is reached to prevent thundering herd issues.</td></td><td>long</td></td><td>60000</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.tolerance</td></td><td>Behavior for tolerating errors during connector operation. 'none' is the default value and signals that any error will result in an immediate connector task failure; 'all' changes the behavior to skip over problematic records.</td></td><td>string</td></td><td>none</td></td><td>[none, all]</td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.log.enable</td></td><td>If true, write each error and the details of the failed operation and problematic record to the Connect application log. This is 'false' by default, so that only errors that are not tolerated are reported.</td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.log.include.messages</td></td><td>Whether to the include in the log the Connect record that resulted in a failure. This is 'false' by default, which will prevent record keys, values, and headers from being written to log files, although some information such as topic and partition number will still be logged.</td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.deadletterqueue.topic.name</td></td><td>The name of the topic to be used as the dead letter queue (DLQ) for messages that result in an error when processed by this sink connector, or its transformations or converters. The topic name is blank by default, which means that no messages are to be recorded in the DLQ.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.deadletterqueue.topic.replication.factor</td></td><td>Replication factor used to create the dead letter queue topic when it doesn't already exist.</td></td><td>short</td></td><td>3</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.deadletterqueue.context.headers.enable</td></td><td>If true, add headers containing error context to the messages written to the dead letter queue. To avoid clashing with headers from the original record, all error context header keys, all error context header keys will start with <code>__connect.errors.</code></td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>medium</td></td></tr>
+</tbody></table>
diff --git a/21/generated/source_connector_config.html b/21/generated/source_connector_config.html
index e69de29..b29bfab 100644
--- a/21/generated/source_connector_config.html
+++ b/21/generated/source_connector_config.html
@@ -0,0 +1,36 @@
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>name</td></td><td>Globally unique name to use for this connector.</td></td><td>string</td></td><td></td></td><td>non-empty string without ISO control characters</td></td><td>high</td></td></tr>
+<tr>
+<td>connector.class</td></td><td>Name or alias of the class for this connector. Must be a subclass of org.apache.kafka.connect.connector.Connector. If the connector is org.apache.kafka.connect.file.FileStreamSinkConnector, you can either specify this full name,  or use "FileStreamSink" or "FileStreamSinkConnector" to make the configuration a bit shorter</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>tasks.max</td></td><td>Maximum number of tasks to use for this connector.</td></td><td>int</td></td><td>1</td></td><td>[1,...]</td></td><td>high</td></td></tr>
+<tr>
+<td>key.converter</td></td><td>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>value.converter</td></td><td>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</td></td><td>class</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>header.converter</td></td><td>HeaderConverter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the header values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro. By default, the SimpleHeaderConverter is used to serialize header values to strings and deseria [...]
+<tr>
+<td>config.action.reload</td></td><td>The action that Connect should take on the connector when changes in external configuration providers result in a change in the connector's configuration properties. A value of 'none' indicates that Connect will do nothing. A value of 'restart' indicates that Connect should restart/reload the connector with the updated configuration properties.The restart may actually be scheduled in the future if the external configuration provider indicates that a  [...]
+<tr>
+<td>transforms</td></td><td>Aliases for the transformations to be applied to records.</td></td><td>list</td></td><td>""</td></td><td>non-null string, unique transformation aliases</td></td><td>low</td></td></tr>
+<tr>
+<td>errors.retry.timeout</td></td><td>The maximum duration in milliseconds that a failed operation will be reattempted. The default is 0, which means no retries will be attempted. Use -1 for infinite retries.</td></td><td>long</td></td><td>0</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.retry.delay.max.ms</td></td><td>The maximum duration in milliseconds between consecutive retry attempts. Jitter will be added to the delay once this limit is reached to prevent thundering herd issues.</td></td><td>long</td></td><td>60000</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.tolerance</td></td><td>Behavior for tolerating errors during connector operation. 'none' is the default value and signals that any error will result in an immediate connector task failure; 'all' changes the behavior to skip over problematic records.</td></td><td>string</td></td><td>none</td></td><td>[none, all]</td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.log.enable</td></td><td>If true, write each error and the details of the failed operation and problematic record to the Connect application log. This is 'false' by default, so that only errors that are not tolerated are reported.</td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>errors.log.include.messages</td></td><td>Whether to the include in the log the Connect record that resulted in a failure. This is 'false' by default, which will prevent record keys, values, and headers from being written to log files, although some information such as topic and partition number will still be logged.</td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>medium</td></td></tr>
+</tbody></table>
diff --git a/21/generated/streams_config.html b/21/generated/streams_config.html
index e69de29..255de5c 100644
--- a/21/generated/streams_config.html
+++ b/21/generated/streams_config.html
@@ -0,0 +1,88 @@
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>application.id</td></td><td>An identifier for the stream processing application. Must be unique within the Kafka cluster. It is used as 1) the default client-id prefix, 2) the group-id for membership management, 3) the changelog topic prefix.</td></td><td>string</td></td><td></td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>bootstrap.servers</td></td><td>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&mdash;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 me [...]
+<tr>
+<td>replication.factor</td></td><td>The replication factor for change log topics and repartition topics created by the stream processing application.</td></td><td>int</td></td><td>1</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>state.dir</td></td><td>Directory location for state store.</td></td><td>string</td></td><td>/tmp/kafka-streams</td></td><td></td></td><td>high</td></td></tr>
+<tr>
+<td>cache.max.bytes.buffering</td></td><td>Maximum number of memory bytes to be used for buffering across all threads</td></td><td>long</td></td><td>10485760</td></td><td>[0,...]</td></td><td>medium</td></td></tr>
+<tr>
+<td>client.id</td></td><td>An ID prefix string used for the client IDs of internal consumer, producer and restore-consumer, with pattern '<client.id>-StreamThread-<threadSequenceNumber>-<consumer|producer|restore-consumer>'.</td></td><td>string</td></td><td>""</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>default.deserialization.exception.handler</td></td><td>Exception handling class that implements the <code>org.apache.kafka.streams.errors.DeserializationExceptionHandler</code> interface.</td></td><td>class</td></td><td>org.apache.kafka.streams.errors.LogAndFailExceptionHandler</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>default.key.serde</td></td><td> Default serializer / deserializer class for key that implements the <code>org.apache.kafka.common.serialization.Serde</code> interface. Note when windowed serde class is used, one needs to set the inner serde class that implements the <code>org.apache.kafka.common.serialization.Serde</code> interface via 'default.windowed.key.serde.inner' or 'default.windowed.value.serde.inner' as well</td></td><td>class</td></td><td>org.apache.kafka.common.serializati [...]
+<tr>
+<td>default.production.exception.handler</td></td><td>Exception handling class that implements the <code>org.apache.kafka.streams.errors.ProductionExceptionHandler</code> interface.</td></td><td>class</td></td><td>org.apache.kafka.streams.errors.DefaultProductionExceptionHandler</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>default.timestamp.extractor</td></td><td>Default timestamp extractor class that implements the <code>org.apache.kafka.streams.processor.TimestampExtractor</code> interface.</td></td><td>class</td></td><td>org.apache.kafka.streams.processor.FailOnInvalidTimestamp</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>default.value.serde</td></td><td>Default serializer / deserializer class for value that implements the <code>org.apache.kafka.common.serialization.Serde</code> interface. Note when windowed serde class is used, one needs to set the inner serde class that implements the <code>org.apache.kafka.common.serialization.Serde</code> interface via 'default.windowed.key.serde.inner' or 'default.windowed.value.serde.inner' as well</td></td><td>class</td></td><td>org.apache.kafka.common.serializ [...]
+<tr>
+<td>max.task.idle.ms</td></td><td>Maximum amount of time a stream task will stay idle when not all of its partition buffers contain records, to avoid potential out-of-order record processing across multiple input streams.</td></td><td>long</td></td><td>0</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>num.standby.replicas</td></td><td>The number of standby replicas for each task.</td></td><td>int</td></td><td>0</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>num.stream.threads</td></td><td>The number of threads to execute stream processing.</td></td><td>int</td></td><td>1</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>processing.guarantee</td></td><td>The processing guarantee that should be used. Possible values are <code>at_least_once</code> (default) and <code>exactly_once</code>. Note that exactly-once processing requires a cluster of at least three brokers by default what is the recommended setting for production; for development you can change this, by adjusting broker setting <code>transaction.state.log.replication.factor</code> and <code>transaction.state.log.min.isr</code>.</td></td><td>st [...]
+<tr>
+<td>security.protocol</td></td><td>Protocol used to communicate with brokers. Valid values are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL.</td></td><td>string</td></td><td>PLAINTEXT</td></td><td></td></td><td>medium</td></td></tr>
+<tr>
+<td>topology.optimization</td></td><td>A configuration telling Kafka Streams if it should optimize the topology, disabled by default</td></td><td>string</td></td><td>none</td></td><td>[none, all]</td></td><td>medium</td></td></tr>
+<tr>
+<td>application.server</td></td><td>A host:port pair pointing to an embedded user defined endpoint that can be used for discovering the locations of state stores within a single KafkaStreams application</td></td><td>string</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>buffered.records.per.partition</td></td><td>Maximum number of records to buffer per partition.</td></td><td>int</td></td><td>1000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>commit.interval.ms</td></td><td>The frequency with which to save the position of the processor. (Note, if <code>processing.guarantee</code> is set to <code>exactly_once</code>, the default value is <code>100</code>, otherwise the default value is <code>30000</code>.</td></td><td>long</td></td><td>30000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>connections.max.idle.ms</td></td><td>Close idle connections after the number of milliseconds specified by this config.</td></td><td>long</td></td><td>540000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>metadata.max.age.ms</td></td><td>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.</td></td><td>long</td></td><td>300000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metric.reporters</td></td><td>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.</td></td><td>list</td></td><td>""</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.num.samples</td></td><td>The number of samples maintained to compute metrics.</td></td><td>int</td></td><td>2</td></td><td>[1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.recording.level</td></td><td>The highest recording level for metrics.</td></td><td>string</td></td><td>INFO</td></td><td>[INFO, DEBUG]</td></td><td>low</td></td></tr>
+<tr>
+<td>metrics.sample.window.ms</td></td><td>The window of time a metrics sample is computed over.</td></td><td>long</td></td><td>30000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>partition.grouper</td></td><td>Partition grouper class that implements the <code>org.apache.kafka.streams.processor.PartitionGrouper</code> interface.</td></td><td>class</td></td><td>org.apache.kafka.streams.processor.DefaultPartitionGrouper</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>poll.ms</td></td><td>The amount of time in milliseconds to block waiting for input.</td></td><td>long</td></td><td>100</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>receive.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>32768</td></td><td>[-1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.max.ms</td></td><td>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.</td></td><td>long</td></td><td>1000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>reconnect.backoff.ms</td></td><td>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.</td></td><td>long</td></td><td>50</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>request.timeout.ms</td></td><td>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.</td></td><td>int</td></td><td>40000</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>retries</td></td><td>Setting a value greater than zero will cause the client to resend any request that fails with a potentially transient error.</td></td><td>int</td></td><td>0</td></td><td>[0,...,2147483647]</td></td><td>low</td></td></tr>
+<tr>
+<td>retry.backoff.ms</td></td><td>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.</td></td><td>long</td></td><td>100</td></td><td>[0,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>rocksdb.config.setter</td></td><td>A Rocks DB config setter class or class name that implements the <code>org.apache.kafka.streams.state.RocksDBConfigSetter</code> interface</td></td><td>class</td></td><td>null</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>send.buffer.bytes</td></td><td>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.</td></td><td>int</td></td><td>131072</td></td><td>[-1,...]</td></td><td>low</td></td></tr>
+<tr>
+<td>state.cleanup.delay.ms</td></td><td>The amount of time in milliseconds to wait before deleting state when a partition has migrated. Only state directories that have not been modified for at least <code>state.cleanup.delay.ms</code> will be removed</td></td><td>long</td></td><td>600000</td></td><td></td></td><td>low</td></td></tr>
+<tr>
+<td>upgrade.from</td></td><td>Allows upgrading from versions 0.10.0/0.10.1/0.10.2/0.11.0/1.0/1.1 to version 1.2 (or newer) in a backward compatible way. When upgrading from 1.2 to a newer version it is not required to specify this config.Default is null. Accepted values are "0.10.0", "0.10.1", "0.10.2", "0.11.0", "1.0", "1.1" (for upgrading from the corresponding old version).</td></td><td>string</td></td><td>null</td></td><td>[null, 0.10.0, 0.10.1, 0.10.2, 0.11.0, 1.0, 1.1]</td></td><td [...]
+<tr>
+<td>windowstore.changelog.additional.retention.ms</td></td><td>Added to a windows maintainMs to ensure data is not deleted from the log prematurely. Allows for clock drift. Default is 1 day</td></td><td>long</td></td><td>86400000</td></td><td></td></td><td>low</td></td></tr>
+</tbody></table>
diff --git a/21/generated/topic_config.html b/21/generated/topic_config.html
index e69de29..24a9505 100644
--- a/21/generated/topic_config.html
+++ b/21/generated/topic_config.html
@@ -0,0 +1,61 @@
+<table class="data-table"><tbody>
+<tr>
+<th>Name</th>
+<th>Description</th>
+<th>Type</th>
+<th>Default</th>
+<th>Valid Values</th>
+<th>Server Default Property</th>
+<th>Importance</th>
+</tr>
+<tr>
+<td>cleanup.policy</td></td><td>A string that is either "delete" or "compact". This string designates the retention policy to use on old log segments. The default policy ("delete") will discard old segments when their retention time or size limit has been reached. The "compact" setting will enable <a href="#compaction">log compaction</a> on the topic.</td></td><td>list</td></td><td>delete</td></td><td>[compact, delete]</td></td><td>log.cleanup.policy</td></td><td>medium</td></td></tr>
+<tr>
+<td>compression.type</td></td><td>Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer.</td></td><td>string</td></td><td>producer</td></td><td>[uncompressed, zstd, lz4, snappy, gzip, producer]</td></td><td>compression.type</td></td><t [...]
+<tr>
+<td>delete.retention.ms</td></td><td>The amount of time to retain delete tombstone markers for <a href="#compaction">log compacted</a> topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage (otherwise delete tombstones may be collected before they complete their scan).</td></td><td>long</td></td><td>86400000</td></td><td>[0,...]</td></td><td>log.cleaner.delete.ret [...]
+<tr>
+<td>file.delete.delay.ms</td></td><td>The time to wait before deleting a file from the filesystem</td></td><td>long</td></td><td>60000</td></td><td>[0,...]</td></td><td>log.segment.delete.delay.ms</td></td><td>medium</td></td></tr>
+<tr>
+<td>flush.messages</td></td><td>This setting allows specifying an interval at which we will force an fsync of data written to the log. For example if this was set to 1 we would fsync after every message; if it were 5 we would fsync after every five messages. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient. This setting can be overridden on a per-topic basis (see <a href="#to [...]
+<tr>
+<td>flush.ms</td></td><td>This setting allows specifying a time interval at which we will force an fsync of data written to the log. For example if this was set to 1000 we would fsync after 1000 ms had passed. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.</td></td><td>long</td></td><td>9223372036854775807</td></td><td>[0,...]</td></td><td>log.flush.interval.ms</td></td><t [...]
+<tr>
+<td>follower.replication.throttled.replicas</td></td><td>A list of replicas for which log replication should be throttled on the follower side. The list should describe a set of replicas in the form [PartitionId]:[BrokerId],[PartitionId]:[BrokerId]:... or alternatively the wildcard '*' can be used to throttle all replicas for this topic.</td></td><td>list</td></td><td>""</td></td><td>[partitionId],[brokerId]:[partitionId],[brokerId]:...</td></td><td>follower.replication.throttled.replica [...]
+<tr>
+<td>index.interval.bytes</td></td><td>This setting controls how frequently Kafka adds an index entry to its offset index. The default setting ensures that we index a message roughly every 4096 bytes. More indexing allows reads to jump closer to the exact position in the log but makes the index larger. You probably don't need to change this.</td></td><td>int</td></td><td>4096</td></td><td>[0,...]</td></td><td>log.index.interval.bytes</td></td><td>medium</td></td></tr>
+<tr>
+<td>leader.replication.throttled.replicas</td></td><td>A list of replicas for which log replication should be throttled on the leader side. The list should describe a set of replicas in the form [PartitionId]:[BrokerId],[PartitionId]:[BrokerId]:... or alternatively the wildcard '*' can be used to throttle all replicas for this topic.</td></td><td>list</td></td><td>""</td></td><td>[partitionId],[brokerId]:[partitionId],[brokerId]:...</td></td><td>leader.replication.throttled.replicas</td> [...]
+<tr>
+<td>max.message.bytes</td></td><td><p>The largest record batch size allowed by Kafka. If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that the they can fetch record batches this large.</p><p>In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in th [...]
+<tr>
+<td>message.format.version</td></td><td>Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as they [...]
+<tr>
+<td>message.timestamp.difference.max.ms</td></td><td>The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. This configuration is ignored if message.timestamp.type=LogAppendTime.</td></td><td>long</td></td><td>9223372036854775807</td></td><td>[0,...]</td></td><td>log.message.timestamp.difference. [...]
+<tr>
+<td>message.timestamp.type</td></td><td>Define whether the timestamp in the message is message create time or log append time. The value should be either `CreateTime` or `LogAppendTime`</td></td><td>string</td></td><td>CreateTime</td></td><td>[CreateTime, LogAppendTime]</td></td><td>log.message.timestamp.type</td></td><td>medium</td></td></tr>
+<tr>
+<td>min.cleanable.dirty.ratio</td></td><td>This configuration controls how frequently the log compactor will attempt to clean the log (assuming <a href="#compaction">log compaction</a> is enabled). By default we will avoid cleaning a log where more than 50% of the log has been compacted. This ratio bounds the maximum space wasted in the log by duplicates (at 50% at most 50% of the log could be duplicates). A higher ratio will mean fewer, more efficient cleanings but will mean more wasted [...]
+<tr>
+<td>min.compaction.lag.ms</td></td><td>The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.</td></td><td>long</td></td><td>0</td></td><td>[0,...]</td></td><td>log.cleaner.min.compaction.lag.ms</td></td><td>medium</td></td></tr>
+<tr>
+<td>min.insync.replicas</td></td><td>When a producer sets acks to "all" (or "-1"), this configuration specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend).<br>When used together, <code>min.insync.replicas</code> and <code>acks</code> allow you to enforce greater durability guarantees. A typical sce [...]
+<tr>
+<td>preallocate</td></td><td>True if we should preallocate the file on disk when creating a new log segment.</td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>log.preallocate</td></td><td>medium</td></td></tr>
+<tr>
+<td>retention.bytes</td></td><td>This configuration controls the maximum size a partition (which consists of log segments) can grow to before we will discard old log segments to free up space if we are using the "delete" retention policy. By default there is no size limit only a time limit. Since this limit is enforced at the partition level, multiply it by the number of partitions to compute the topic retention in bytes.</td></td><td>long</td></td><td>-1</td></td><td></td></td><td>log.r [...]
+<tr>
+<td>retention.ms</td></td><td>This configuration controls the maximum time we will retain a log before we will discard old log segments to free up space if we are using the "delete" retention policy. This represents an SLA on how soon consumers must read their data. If set to -1, no time limit is applied.</td></td><td>long</td></td><td>604800000</td></td><td></td></td><td>log.retention.ms</td></td><td>medium</td></td></tr>
+<tr>
+<td>segment.bytes</td></td><td>This configuration controls the segment file size for the log. Retention and cleaning is always done a file at a time so a larger segment size means fewer files but less granular control over retention.</td></td><td>int</td></td><td>1073741824</td></td><td>[14,...]</td></td><td>log.segment.bytes</td></td><td>medium</td></td></tr>
+<tr>
+<td>segment.index.bytes</td></td><td>This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.</td></td><td>int</td></td><td>10485760</td></td><td>[0,...]</td></td><td>log.index.size.max.bytes</td></td><td>medium</td></td></tr>
+<tr>
+<td>segment.jitter.ms</td></td><td>The maximum random jitter subtracted from the scheduled segment roll time to avoid thundering herds of segment rolling</td></td><td>long</td></td><td>0</td></td><td>[0,...]</td></td><td>log.roll.jitter.ms</td></td><td>medium</td></td></tr>
+<tr>
+<td>segment.ms</td></td><td>This configuration controls the period of time after which Kafka will force the log to roll even if the segment file isn't full to ensure that retention can delete or compact old data.</td></td><td>long</td></td><td>604800000</td></td><td>[1,...]</td></td><td>log.roll.ms</td></td><td>medium</td></td></tr>
+<tr>
+<td>unclean.leader.election.enable</td></td><td>Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss.</td></td><td>boolean</td></td><td>false</td></td><td></td></td><td>unclean.leader.election.enable</td></td><td>medium</td></td></tr>
+<tr>
+<td>message.downconversion.enable</td></td><td>This configuration controls whether down-conversion of message formats is enabled to satisfy consume requests. When set to <code>false</code>, broker will not perform down-conversion for consumers expecting an older message format. The broker responds with <code>UNSUPPORTED_VERSION</code> error for consume requests from such older clients. This configurationdoes not apply to any message format conversion that might be required for replicatio [...]
+</tbody></table>


Mime
View raw message