KafkaAPI实战

忘是亡心i 2022-04-25 01:48 163阅读 0赞

新旧API使用 Flume和Kafka集成：

Kafka有两套API: 过时的API 和新API

## 准备工作 ##

## Kafka生产者API ##

### 旧 ###

### 高级 ###

### 生产者带回调函数 ###

### 自定义分区 ###

需求:将所有数据存储到topic的第0号分区上

## Kafka消费者 ##

### 旧 ###

使用低级API读取指定topic，指定partition,指定offset的数据。

1消费者使用低级API 的主要步骤：

<table> 
 <thead> 
 <tr> 
 <th>步骤</th> 
 <th>主要工作</th> 
 </tr> 
 </thead> 
 <tbody> 
 <tr> 
 <td>1</td> 
 <td>根据指定的分区从主题元数据中找到主副本</td> 
 </tr> 
 <tr> 
 <td>2</td> 
 <td>获取分区最新的消费进度</td> 
 </tr> 
 <tr> 
 <td>3</td> 
 <td>从主副本拉取分区的消息</td> 
 </tr> 
 <tr> 
 <td>4</td> 
 <td>识别主副本的变化，重试</td> 
 </tr> 
 </tbody> 
</table>

2方法描述：

<table> 
 <thead> 
 <tr> 
 <th>findLeader()</th> 
 <th>客户端向种子节点发送主题元数据，将副本集加入备用节点</th> 
 </tr> 
 </thead> 
 <tbody> 
 <tr> 
 <td>getLastOffset()</td> 
 <td>消费者客户端发送偏移量请求，获取分区最近的偏移量</td> 
 </tr> 
 <tr> 
 <td>run()</td> 
 <td>消费者低级AP I拉取消息的主要方法</td> 
 </tr> 
 <tr> 
 <td>findNewLeader()</td> 
 <td>当分区的主副本节点发生故障，客户将要找出新的主副本</td> 
 </tr> 
 </tbody> 
</table>

<table> 
 <tbody> 
 <tr> 
 <td><pre>1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 </pre></td> 
 <td><pre>import java.nio.ByteBuffer; import java.util.ArrayList; import java.util.Collections; import java.util.HashMap; import java.util.List; import java.util.Map; import kafka.api.FetchRequest; import kafka.api.FetchRequestBuilder; import kafka.api.PartitionOffsetRequestInfo; import kafka.cluster.BrokerEndPoint; import kafka.common.ErrorMapping; import kafka.common.TopicAndPartition; import kafka.javaapi.FetchResponse; import kafka.javaapi.OffsetResponse; import kafka.javaapi.PartitionMetadata; import kafka.javaapi.TopicMetadata; import kafka.javaapi.TopicMetadataRequest; import kafka.javaapi.consumer.SimpleConsumer; import kafka.message.MessageAndOffset; public class OldConsumer {
 private List&lt;String&gt; m_replicaBrokers = new ArrayList&lt;&gt;(); public OldConsumer() {
 m_replicaBrokers = new ArrayList&lt;&gt;(); } public static void main(String args[]) {
 OldConsumer example = new OldConsumer(); // 最大读取消息数量 long maxReads = Long.parseLong("3"); // 要订阅的topic String topic = "first"; // 要查找的分区 int partition = Integer.parseInt("0"); // broker节点的ip List&lt;String&gt; seeds = new ArrayList&lt;&gt;(); seeds.add("192.168.1.101"); seeds.add("192.168.1.102"); seeds.add("192.168.1.103"); // 端口 int port = Integer.parseInt("9092"); try {
 example.run(maxReads, topic, partition, seeds, port); } catch (Exception e) {
 System.out.println("Oops:" + e); e.printStackTrace(); } } public void run(long a_maxReads, String a_topic, int a_partition, List&lt;String&gt; a_seedBrokers, int a_port) throws Exception {
 // 获取指定Topic partition的元数据 PartitionMetadata metadata = findLeader(a_seedBrokers, a_port, a_topic, a_partition); if (metadata == null) {
 System.out.println("Can't find metadata for Topic and Partition. Exiting"); return; } if (metadata.leader() == null) {
 System.out.println("Can't find Leader for Topic and Partition. Exiting"); return; } String leadBroker = metadata.leader().host(); String clientName = "Client_" + a_topic + "_" + a_partition; SimpleConsumer consumer = new SimpleConsumer(leadBroker, a_port, 100000, 64 * 1024, clientName); long readOffset = getLastOffset(consumer, a_topic, a_partition, kafka.api.OffsetRequest.EarliestTime(), clientName); int numErrors = 0; while (a_maxReads &gt; 0) {
 if (consumer == null) {
 consumer = new SimpleConsumer(leadBroker, a_port, 100000, 64 * 1024, clientName); } FetchRequest req = new FetchRequestBuilder().clientId(clientName).addFetch(a_topic, a_partition, readOffset, 100000).build(); FetchResponse fetchResponse = consumer.fetch(req); if (fetchResponse.hasError()) {
 numErrors++; // Something went wrong! short code = fetchResponse.errorCode(a_topic, a_partition); System.out.println("Error fetching data from the Broker:" + leadBroker + " Reason: " + code); if (numErrors &gt; 5) break; if (code == ErrorMapping.OffsetOutOfRangeCode()) {
 // We asked for an invalid offset. For simple case ask for // the last element to reset readOffset = getLastOffset(consumer, a_topic, a_partition, kafka.api.OffsetRequest.LatestTime(), clientName); continue; } consumer.close(); consumer = null; leadBroker = findNewLeader(leadBroker, a_topic, a_partition, a_port); continue; } numErrors = 0; long numRead = 0; for (MessageAndOffset messageAndOffset : fetchResponse.messageSet(a_topic, a_partition)) {
 long currentOffset = messageAndOffset.offset(); if (currentOffset &lt; readOffset) {
 System.out.println("Found an old offset: " + currentOffset + " Expecting: " + readOffset); continue; } readOffset = messageAndOffset.nextOffset(); ByteBuffer payload = messageAndOffset.message().payload(); byte[] bytes = new byte[payload.limit()]; payload.get(bytes); System.out.println(String.valueOf(messageAndOffset.offset()) + ": " + new String(bytes, "UTF-8")); numRead++; a_maxReads--; } if (numRead == 0) {
 try {
 Thread.sleep(1000); } catch (InterruptedException ie) {
 } } } if (consumer != null) consumer.close(); } public static long getLastOffset(SimpleConsumer consumer, String topic, int partition, long whichTime, String clientName) {
 TopicAndPartition topicAndPartition = new TopicAndPartition(topic, partition); Map&lt;TopicAndPartition, PartitionOffsetRequestInfo&gt; requestInfo = new HashMap&lt;TopicAndPartition, PartitionOffsetRequestInfo&gt;(); requestInfo.put(topicAndPartition, new PartitionOffsetRequestInfo(whichTime, 1)); kafka.javaapi.OffsetRequest request = new kafka.javaapi.OffsetRequest(requestInfo, kafka.api.OffsetRequest.CurrentVersion(), clientName); OffsetResponse response = consumer.getOffsetsBefore(request); if (response.hasError()) {
 System.out.println("Error fetching data Offset Data the Broker. Reason: " + response.errorCode(topic, partition)); return 0; } long[] offsets = response.offsets(topic, partition); return offsets[0]; } private String findNewLeader(String a_oldLeader, String a_topic, int a_partition, int a_port) throws Exception {
 for (int i = 0; i &lt; 3; i++) {
 boolean goToSleep = false; PartitionMetadata metadata = findLeader(m_replicaBrokers, a_port, a_topic, a_partition); if (metadata == null) {
 goToSleep = true; } else if (metadata.leader() == null) {
 goToSleep = true; } else if (a_oldLeader.equalsIgnoreCase(metadata.leader().host()) &amp;&amp; i == 0) {
 // first time through if the leader hasn't changed give // ZooKeeper a second to recover // second time, assume the broker did recover before failover, // or it was a non-Broker issue // goToSleep = true; } else {
 return metadata.leader().host(); } if (goToSleep) {
 Thread.sleep(1000); } } System.out.println("Unable to find new leader after Broker failure. Exiting"); throw new Exception("Unable to find new leader after Broker failure. Exiting"); } private PartitionMetadata findLeader(List&lt;String&gt; a_seedBrokers, int a_port, String a_topic, int a_partition) {
 PartitionMetadata returnMetaData = null; loop: for (String seed : a_seedBrokers) {
 SimpleConsumer consumer = null; try {
 consumer = new SimpleConsumer(seed, a_port, 100000, 64 * 1024, "leaderLookup"); List&lt;String&gt; topics = Collections.singletonList(a_topic); TopicMetadataRequest req = new TopicMetadataRequest(topics); kafka.javaapi.TopicMetadataResponse resp = consumer.send(req); List&lt;TopicMetadata&gt; metaData = resp.topicsMetadata(); for (TopicMetadata item : metaData) {
 for (PartitionMetadata part : item.partitionsMetadata()) {
 if (part.partitionId() == a_partition) {
 returnMetaData = part; break loop; } } } } catch (Exception e) {
 System.out.println("Error communicating with Broker [" + seed + "] to find Leader for [" + a_topic + ", " + a_partition + "] Reason: " + e); } finally {
 if (consumer != null) consumer.close(); } } if (returnMetaData != null) {
 m_replicaBrokers.clear(); for (BrokerEndPoint replica : returnMetaData.replicas()) {
 m_replicaBrokers.add(replica.host()); } } return returnMetaData; } } </pre></td> 
 </tr> 
 </tbody> 
</table>

![FzomLj.png][]

### 新 ###

![FzIAKJ.png][]

## Kafka拦截器 ##

### 拦截器原理 ###

Producer拦截器(interceptor)在Kafka 0.10版本被引入，主要用于实现clients端的定制化控制逻辑。

对于producer而言，interceptor使得用户在消息发送前以及producer回调逻辑前有机会对消息做一些定制化需求，比如修改消息等。同时，producer允许用户指定多个interceptor按序作用于同一条消息从而形成一个拦截链(interceptor chain)。Intercetpor的实现接口是org.apache.kafka.clients.producer.ProducerInterceptor，其定义的方法包括：

（1）configure(configs)

获取配置信息和初始化数据时调用。

（2）onSend(ProducerRecord)：

该方法封装进KafkaProducer.send方法中，即它运行在用户主线程中。Producer确保在消息被序列化以及计算分区前调用该方法。用户可以在该方法中对消息做任何操作，但最好保证不要修改消息所属的topic和分区，否则会影响目标分区的计算

（3）onAcknowledgement(RecordMetadata, Exception)：

该方法会在消息被应答或消息发送失败时调用，并且通常都是在producer回调逻辑触发之前。onAcknowledgement运行在producer的IO线程中，因此不要在该方法中放入很重的逻辑，否则会拖慢producer的消息发送效率

（4）close：

关闭interceptor，主要用于执行一些资源清理工作

如前所述，interceptor可能被运行在多个线程中，因此在具体实现时用户需要自行确保线程安全。另外倘若指定了多个interceptor，则producer将按照指定顺序调用它们，并仅仅是捕获每个interceptor可能抛出的异常记录到错误日志中而非在向上传递。这在使用过程中要特别留意。

### 案例 ###

#### TimeInterceptor ####

#### CounterInterceptor ####

#### InterceptorProducer ####

![FzTk7R.png][]

### Kafka Streams ###

Apache Kafka开源项目的一个组成部分。是一个功能强大，易于使用的库。用于在Kafka上构建高可分布式、拓展性，容错的应用程序。但是用的不多.目前用Spark和Flink做流式实时计算的比较多。

#### 特点 ####

功能强大 ：高扩展性，弹性，容错

轻量级 ：无需专门的集群 一个库，而不是框架

完全集成：100%的Kafka 0.10.0版本兼容 易于集成到现有的应用程序

实时性： 毫秒级延迟 并非微批处理 窗口允许乱序数据 允许迟到数据

#### 由来 ####

当前已经有非常多的流式处理系统，最知名且应用最多的开源流式处理系统有Spark Streaming和Apache Storm。Apache Storm发展多年，应用广泛，提供记录级别的处理能力，当前也支持SQL on Stream。而Spark Streaming基于Apache Spark，可以非常方便与图计算，SQL处理等集成，功能强大，对于熟悉其它Spark应用开发的用户而言使用门槛低。另外，目前主流的Hadoop发行版，如Cloudera和Hortonworks，都集成了Apache Storm和Apache Spark，使得部署更容易。

既然Apache Spark与Apache Storm拥用如此多的优势，那为何还需要Kafka Stream呢？主要有如下原因。

第一，Spark和Storm都是流式处理框架，而Kafka Stream提供的是一个基于Kafka的流式处理类库。框架要求开发者按照特定的方式去开发逻辑部分，供框架调用。开发者很难了解框架的具体运行方式，从而使得调试成本高，并且使用受限。而Kafka Stream作为流式处理类库，直接提供具体的类给开发者调用，整个应用的运行方式主要由开发者控制，方便使用和调试。

![Fz7SUI.png][]

第二，虽然Cloudera与Hortonworks方便了Storm和Spark的部署，但是这些框架的部署仍然相对复杂。而Kafka Stream作为类库，可以非常方便的嵌入应用程序中，它对应用的打包和部署基本没有任何要求。

第三，就流式处理系统而言，基本都支持Kafka作为数据源。例如Storm具有专门的kafka-spout，而Spark也提供专门的spark-streaming-kafka模块。事实上，Kafka基本上是主流的流式处理系统的标准数据源。换言之，大部分流式系统中都已部署了Kafka，此时使用Kafka Stream的成本非常低。

第四，使用Storm或Spark Streaming时，需要为框架本身的进程预留资源，如Storm的supervisor和Spark on YARN的node manager。即使对于应用实例而言，框架本身也会占用部分资源，如Spark Streaming需要为shuffle和storage预留内存。但是Kafka作为类库不占用系统资源。

第五，由于Kafka本身提供数据持久化，因此Kafka Stream提供滚动部署和滚动升级以及重新计算的能力。

第六，由于Kafka Consumer Rebalance机制，Kafka Stream可以在线动态调整并行度。

#### 数据清洗 ####

![Fz7GqJ.png][]

##### LogProcessor #####

##### MyStream #####

![FzHkJx.png][]

### Kafka与Flume比较 ###

<table> 
 <thead> 
 <tr> 
 <th>flume</th> 
 <th>Kafka</th> 
 </tr> 
 </thead> 
 <tbody> 
 <tr> 
 <td>cloudera公司研发:</td> 
 <td>linkedin公司研发:</td> 
 </tr> 
 <tr> 
 <td>适合多个生产者；</td> 
 <td>适合数据下游消费众多的情况；</td> 
 </tr> 
 <tr> 
 <td>适合下游数据消费者不多的情况；</td> 
 <td>适合数据安全性要求较高的操作，支持replication。</td> 
 </tr> 
 <tr> 
 <td>适合数据安全性要求不高的操作；</td> 
 <td></td> 
 </tr> 
 <tr> 
 <td>适合与Hadoop生态圈对接的操作。</td> 
 </tr> 
 </tbody> 
</table>

常用模型

线上数据 —> flume—> kafka —> flume(根据情景增删该流程) —> HDFS

#### Flume和Kafka集成 ####

启动消费者

<table> 
 <tbody> 
 <tr> 
 <td><pre>1 </pre></td> 
 <td><pre>[hadoop@datanode2 kafka]$ bin/kafka-console-consumer.sh --zookeeper datanode1:2181 --from-beginning --topic three </pre></td> 
 </tr> 
 </tbody> 
</table>

启动flume

<table> 
 <tbody> 
 <tr> 
 <td><pre>1 </pre></td> 
 <td><pre>[hadoop@datanode1 flume]$ bin/flume-ng agent -c conf/ -n a1 -f job/flume-kafka.conf </pre></td> 
 </tr> 
 </tbody> 
</table>

测试脚本

![kSFRxg.png][]

### Kafka配置信息 ###

#### Broker配置信息 ####

<table> 
 <thead> 
 <tr> 
 <th>属性</th> 
 <th>默认值</th> 
 <th>描述</th> 
 </tr> 
 </thead> 
 <tbody> 
 <tr> 
 <td>broker.id</td> 
 <td></td> 
 <td>必填参数，broker的唯一标识</td> 
 </tr> 
 <tr> 
 <td>log.dirs</td> 
 <td>/tmp/kafka-logs</td> 
 <td>Kafka数据存放的目录。可以指定多个目录，中间用逗号分隔，当新partition被创建的时会被存放到当前存放partition最少的目录。</td> 
 </tr> 
 <tr> 
 <td>port</td> 
 <td>9092</td> 
 <td>BrokerServer接受客户端连接的端口号</td> 
 </tr> 
 <tr> 
 <td>zookeeper.connect</td> 
 <td>null</td> 
 <td>Zookeeper的连接串，格式为：hostname1:port1,hostname2:port2,hostname3:port3。可以填一个或多个，为了提高可靠性，建议都填上。注意，此配置允许我们指定一个zookeeper路径来存放此kafka集群的所有数据，为了与其他应用集群区分开，建议在此配置中指定本集群存放目录，格式为：hostname1:port1,hostname2:port2,hostname3:port3/chroot/path 。需要注意的是，消费者的参数要和此参数一致。</td> 
 </tr> 
 <tr> 
 <td>message.max.bytes</td> 
 <td>1000000</td> 
 <td>服务器可以接收到的最大的消息大小。注意此参数要和consumer的maximum.message.size大小一致，否则会因为生产者生产的消息太大导致消费者无法消费。</td> 
 </tr> 
 <tr> 
 <td>num.io.threads</td> 
 <td>8</td> 
 <td>服务器用来执行读写请求的IO线程数，此参数的数量至少要等于服务器上磁盘的数量。</td> 
 </tr> 
 <tr> 
 <td>queued.max.requests</td> 
 <td>500</td> 
 <td>I/O线程可以处理请求的队列大小，若实际请求数超过此大小，网络线程将停止接收新的请求。</td> 
 </tr> 
 <tr> 
 <td>socket.send.buffer.bytes</td> 
 <td>100 * 1024</td> 
 <td>The SO_SNDBUFF buffer the server prefers for socket connections.</td> 
 </tr> 
 <tr> 
 <td>socket.receive.buffer.bytes</td> 
 <td>100 * 1024</td> 
 <td>The SO_RCVBUFF buffer the server prefers for socket connections.</td> 
 </tr> 
 <tr> 
 <td>socket.request.max.bytes</td> 
 <td>100 1024 1024</td> 
 <td>服务器允许请求的最大值， 用来防止内存溢出，其值应该小于 Java heap size.</td> 
 </tr> 
 <tr> 
 <td>num.partitions</td> 
 <td>1</td> 
 <td>默认partition数量，如果topic在创建时没有指定partition数量，默认使用此值，建议改为5</td> 
 </tr> 
 <tr> 
 <td>log.segment.bytes</td> 
 <td>1024 1024 1024</td> 
 <td>Segment文件的大小，超过此值将会自动新建一个segment，此值可以被topic级别的参数覆盖。</td> 
 </tr> 
 <tr> 
 <td>log.roll.{ms,hours}</td> 
 <td>24 * 7 hours</td> 
 <td>新建segment文件的时间，此值可以被topic级别的参数覆盖。</td> 
 </tr> 
 <tr> 
 <td>log.retention.{ms,minutes,hours}</td> 
 <td>7 days</td> 
 <td>Kafka segment log的保存周期，保存周期超过此时间日志就会被删除。此参数可以被topic级别参数覆盖。数据量大时，建议减小此值。</td> 
 </tr> 
 <tr> 
 <td>log.retention.bytes</td> 
 <td>-1</td> 
 <td>每个partition的最大容量，若数据量超过此值，partition数据将会被删除。注意这个参数控制的是每个partition而不是topic。此参数可以被log级别参数覆盖。</td> 
 </tr> 
 <tr> 
 <td>log.retention.check.interval.ms</td> 
 <td>5 minutes</td> 
 <td>删除策略的检查周期</td> 
 </tr> 
 <tr> 
 <td>auto.create.topics.enable</td> 
 <td>true</td> 
 <td>自动创建topic参数，建议此值设置为false，严格控制topic管理，防止生产者错写topic。</td> 
 </tr> 
 <tr> 
 <td>default.replication.factor</td> 
 <td>1</td> 
 <td>默认副本数量，建议改为2。</td> 
 </tr> 
 <tr> 
 <td>replica.lag.time.max.ms</td> 
 <td>10000</td> 
 <td>在此窗口时间内没有收到follower的fetch请求，leader会将其从ISR(in-sync replicas)中移除。</td> 
 </tr> 
 <tr> 
 <td>replica.lag.max.messages</td> 
 <td>4000</td> 
 <td>如果replica节点落后leader节点此值大小的消息数量，leader节点就会将其从ISR中移除。</td> 
 </tr> 
 <tr> 
 <td>replica.socket.timeout.ms</td> 
 <td>30 * 1000</td> 
 <td>replica向leader发送请求的超时时间。</td> 
 </tr> 
 <tr> 
 <td>replica.socket.receive.buffer.bytes</td> 
 <td>64 * 1024</td> 
 <td>The socket receive buffer for network requests to the leader for replicating data.</td> 
 </tr> 
 <tr> 
 <td>replica.fetch.max.bytes</td> 
 <td>1024 * 1024</td> 
 <td>The number of byes of messages to attempt to fetch for each partition in the fetch requests the replicas send to the leader.</td> 
 </tr> 
 <tr> 
 <td>replica.fetch.wait.max.ms</td> 
 <td>500</td> 
 <td>The maximum amount of time to wait time for data to arrive on the leader in the fetch requests sent by the replicas to the leader.</td> 
 </tr> 
 <tr> 
 <td>num.replica.fetchers</td> 
 <td>1</td> 
 <td>Number of threads used to replicate messages from leaders. Increasing this value can increase the degree of I/O parallelism in the follower broker.</td> 
 </tr> 
 <tr> 
 <td>fetch.purgatory.purge.interval.requests</td> 
 <td>1000</td> 
 <td>The purge interval (in number of requests) of the fetch request purgatory.</td> 
 </tr> 
 <tr> 
 <td>zookeeper.session.timeout.ms</td> 
 <td>6000</td> 
 <td>ZooKeeper session 超时时间。如果在此时间内server没有向zookeeper发送心跳，zookeeper就会认为此节点已挂掉。 此值太低导致节点容易被标记死亡；若太高，.会导致太迟发现节点死亡。</td> 
 </tr> 
 <tr> 
 <td>zookeeper.connection.timeout.ms</td> 
 <td>6000</td> 
 <td>客户端连接zookeeper的超时时间。</td> 
 </tr> 
 <tr> 
 <td>zookeeper.sync.time.ms</td> 
 <td>2000</td> 
 <td>H ZK follower落后 ZK leader的时间。</td> 
 </tr> 
 <tr> 
 <td>controlled.shutdown.enable</td> 
 <td>true</td> 
 <td>允许broker shutdown。如果启用，broker在关闭自己之前会把它上面的所有leaders转移到其它brokers上，建议启用，增加集群稳定性。</td> 
 </tr> 
 <tr> 
 <td>auto.leader.rebalance.enable</td> 
 <td>true</td> 
 <td>If this is enabled the controller will automatically try to balance leadership for partitions among the brokers by periodically returning leadership to the “preferred” replica for each partition if it is available.</td> 
 </tr> 
 <tr> 
 <td>leader.imbalance.per.broker.percentage</td> 
 <td>10</td> 
 <td>The percentage of leader imbalance allowed per broker. The controller will rebalance leadership if this ratio goes above the configured value per broker.</td> 
 </tr> 
 <tr> 
 <td>leader.imbalance.check.interval.seconds</td> 
 <td>300</td> 
 <td>The frequency with which to check for leader imbalance.</td> 
 </tr> 
 <tr> 
 <td>offset.metadata.max.bytes</td> 
 <td>4096</td> 
 <td>The maximum amount of metadata to allow clients to save with their offsets.</td> 
 </tr> 
 <tr> 
 <td>connections.max.idle.ms</td> 
 <td>600000</td> 
 <td>Idle connections timeout: the server socket processor threads close the connections that idle more than this.</td> 
 </tr> 
 <tr> 
 <td>num.recovery.threads.per.data.dir</td> 
 <td>1</td> 
 <td>The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.</td> 
 </tr> 
 <tr> 
 <td>unclean.leader.election.enable</td> 
 <td>true</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> 
 </tr> 
 <tr> 
 <td>delete.topic.enable</td> 
 <td>false</td> 
 <td>启用deletetopic参数，建议设置为true。</td> 
 </tr> 
 <tr> 
 <td>offsets.topic.num.partitions</td> 
 <td>50</td> 
 <td>The number of partitions for the offset commit topic. Since changing this after deployment is currently unsupported, we recommend using a higher setting for production (e.g., 100-200).</td> 
 </tr> 
 <tr> 
 <td>offsets.topic.retention.minutes</td> 
 <td>1440</td> 
 <td>Offsets that are older than this age will be marked for deletion. The actual purge will occur when the log cleaner compacts the offsets topic.</td> 
 </tr> 
 <tr> 
 <td>offsets.retention.check.interval.ms</td> 
 <td>600000</td> 
 <td>The frequency at which the offset manager checks for stale offsets.</td> 
 </tr> 
 <tr> 
 <td>offsets.topic.replication.factor</td> 
 <td>3</td> 
 <td>The replication factor for the offset commit topic. A higher setting (e.g., three or four) is recommended in order to ensure higher availability. If the offsets topic is created when fewer brokers than the replication factor then the offsets topic will be created with fewer replicas.</td> 
 </tr> 
 <tr> 
 <td>offsets.topic.segment.bytes</td> 
 <td>104857600</td> 
 <td>Segment size for the offsets topic. Since it uses a compacted topic, this should be kept relatively low in order to facilitate faster log compaction and loads.</td> 
 </tr> 
 <tr> 
 <td>offsets.load.buffer.size</td> 
 <td>5242880</td> 
 <td>An offset load occurs when a broker becomes the offset manager for a set of consumer groups (i.e., when it becomes a leader for an offsets topic partition). This setting corresponds to the batch size (in bytes) to use when reading from the offsets segments when loading offsets into the offset manager’s cache.</td> 
 </tr> 
 <tr> 
 <td>offsets.commit.required.acks</td> 
 <td>-1</td> 
 <td>The number of acknowledgements that are required before the offset commit can be accepted. This is similar to the producer’s acknowledgement setting. In general, the default should not be overridden.</td> 
 </tr> 
 <tr> 
 <td>offsets.commit.timeout.ms</td> 
 <td>5000</td> 
 <td>The offset commit will be delayed until this timeout or the required number of replicas have received the offset commit. This is similar to the producer request timeout.</td> 
 </tr> 
 </tbody> 
</table>

#### Producer配置信息 ####

<table> 
 <thead> 
 <tr> 
 <th>属性</th> 
 <th>默认值</th> 
 <th>描述</th> 
 </tr> 
 </thead> 
 <tbody> 
 <tr> 
 <td>metadata.broker.list</td> 
 <td></td> 
 <td>启动时producer查询brokers的列表，可以是集群中所有brokers的一个子集。注意，这个参数只是用来获取topic的元信息用，producer会从元信息中挑选合适的broker并与之建立socket连接。格式是：host1:port1,host2:port2。</td> 
 </tr> 
 <tr> 
 <td>request.required.acks</td> 
 <td>0</td> 
 <td>参见3.2节介绍</td> 
 </tr> 
 <tr> 
 <td>request.timeout.ms</td> 
 <td>10000</td> 
 <td>Broker等待ack的超时时间，若等待时间超过此值，会返回客户端错误信息。</td> 
 </tr> 
 <tr> 
 <td>producer.type</td> 
 <td>sync</td> 
 <td>同步异步模式。async表示异步，sync表示同步。如果设置成异步模式，可以允许生产者以batch的形式push数据，这样会极大的提高broker性能，推荐设置为异步。</td> 
 </tr> 
 <tr> 
 <td>serializer.class</td> 
 <td>kafka.serializer.DefaultEncoder</td> 
 <td>序列号类，.默认序列化成 byte[] 。</td> 
 </tr> 
 <tr> 
 <td>key.serializer.class</td> 
 <td></td> 
 <td>Key的序列化类，默认同上。</td> 
 </tr> 
 <tr> 
 <td>partitioner.class</td> 
 <td>kafka.producer.DefaultPartitioner</td> 
 <td>Partition类，默认对key进行hash。</td> 
 </tr> 
 <tr> 
 <td>compression.codec</td> 
 <td>none</td> 
 <td>指定producer消息的压缩格式，可选参数为： “none”, “gzip” and “snappy”。关于压缩参见4.1节</td> 
 </tr> 
 <tr> 
 <td>compressed.topics</td> 
 <td>null</td> 
 <td>启用压缩的topic名称。若上面参数选择了一个压缩格式，那么压缩仅对本参数指定的topic有效，若本参数为空，则对所有topic有效。</td> 
 </tr> 
 <tr> 
 <td>message.send.max.retries</td> 
 <td>3</td> 
 <td>Producer发送失败时重试次数。若网络出现问题，可能会导致不断重试。</td> 
 </tr> 
 <tr> 
 <td>retry.backoff.ms</td> 
 <td>100</td> 
 <td>Before each retry, the producer refreshes the metadata of relevant topics to see if a new leader has been elected. Since leader election takes a bit of time, this property specifies the amount of time that the producer waits before refreshing the metadata.</td> 
 </tr> 
 <tr> 
 <td>topic.metadata.refresh.interval.ms</td> 
 <td>600 * 1000</td> 
 <td>The producer generally refreshes the topic metadata from brokers when there is a failure (partition missing, leader not available…). It will also poll regularly (default: every 10min so 600000ms). If you set this to a negative value, metadata will only get refreshed on failure. If you set this to zero, the metadata will get refreshed after each message sent (not recommended). Important note: the refresh happen only AFTER the message is sent, so if the producer never sends a message the metadata is never refreshed</td> 
 </tr> 
 <tr> 
 <td>queue.buffering.max.ms</td> 
 <td>5000</td> 
 <td>启用异步模式时，producer缓存消息的时间。比如我们设置成1000时，它会缓存1秒的数据再一次发送出去，这样可以极大的增加broker吞吐量，但也会造成时效性的降低。</td> 
 </tr> 
 <tr> 
 <td>queue.buffering.max.messages</td> 
 <td>10000</td> 
 <td>采用异步模式时producer buffer 队列里最大缓存的消息数量，如果超过这个数值，producer就会阻塞或者丢掉消息。</td> 
 </tr> 
 <tr> 
 <td>queue.enqueue.timeout.ms</td> 
 <td>-1</td> 
 <td>当达到上面参数值时producer阻塞等待的时间。如果值设置为0，buffer队列满时producer不会阻塞，消息直接被丢掉。若值设置为-1，producer会被阻塞，不会丢消息。</td> 
 </tr> 
 <tr> 
 <td>batch.num.messages</td> 
 <td>200</td> 
 <td>采用异步模式时，一个batch缓存的消息数量。达到这个数量值时producer才会发送消息。</td> 
 </tr> 
 <tr> 
 <td>send.buffer.bytes</td> 
 <td>100 * 1024</td> 
 <td>Socket write buffer size</td> 
 </tr> 
 <tr> 
 <td>client.id</td> 
 <td>“”</td> 
 <td>The client id is a user-specified string sent in each request to help trace calls. It should logically identify the application making the request.</td> 
 </tr> 
 </tbody> 
</table>

#### Consumer配置信息 ####

<table> 
 <thead> 
 <tr> 
 <th>属性</th> 
 <th>默认值</th> 
 <th>描述</th> 
 </tr> 
 </thead> 
 <tbody> 
 <tr> 
 <td>group.id</td> 
 <td></td> 
 <td>Consumer的组ID，相同goup.id的consumer属于同一个组。</td> 
 </tr> 
 <tr> 
 <td>zookeeper.connect</td> 
 <td></td> 
 <td>Consumer的zookeeper连接串，要和broker的配置一致。</td> 
 </tr> 
 <tr> 
 <td>consumer.id</td> 
 <td>null</td> 
 <td>如果不设置会自动生成。</td> 
 </tr> 
 <tr> 
 <td>socket.timeout.ms</td> 
 <td>30 * 1000</td> 
 <td>网络请求的socket超时时间。实际超时时间由max.fetch.wait + socket.timeout.ms 确定。</td> 
 </tr> 
 <tr> 
 <td>socket.receive.buffer.bytes</td> 
 <td>64 * 1024</td> 
 <td>The socket receive buffer for network requests.</td> 
 </tr> 
 <tr> 
 <td>fetch.message.max.bytes</td> 
 <td>1024 * 1024</td> 
 <td>查询topic-partition时允许的最大消息大小。consumer会为每个partition缓存此大小的消息到内存，因此，这个参数可以控制consumer的内存使用量。这个值应该至少比server允许的最大消息大小大，以免producer发送的消息大于consumer允许的消息。</td> 
 </tr> 
 <tr> 
 <td>num.consumer.fetchers</td> 
 <td>1</td> 
 <td>The number fetcher threads used to fetch data.</td> 
 </tr> 
 <tr> 
 <td>auto.commit.enable</td> 
 <td>true</td> 
 <td>如果此值设置为true，consumer会周期性的把当前消费的offset值保存到zookeeper。当consumer失败重启之后将会使用此值作为新开始消费的值。</td> 
 </tr> 
 <tr> 
 <td>auto.commit.interval.ms</td> 
 <td>60 * 1000</td> 
 <td>Consumer提交offset值到zookeeper的周期。</td> 
 </tr> 
 <tr> 
 <td>queued.max.message.chunks</td> 
 <td>2</td> 
 <td>用来被consumer消费的message chunks 数量， 每个chunk可以缓存fetch.message.max.bytes大小的数据量。</td> 
 </tr> 
 <tr> 
 <td>auto.commit.interval.ms</td> 
 <td>60 * 1000</td> 
 <td>Consumer提交offset值到zookeeper的周期。</td> 
 </tr> 
 <tr> 
 <td>queued.max.message.chunks</td> 
 <td>2</td> 
 <td>用来被consumer消费的message chunks 数量， 每个chunk可以缓存fetch.message.max.bytes大小的数据量。</td> 
 </tr> 
 <tr> 
 <td>fetch.min.bytes</td> 
 <td>1</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.</td> 
 </tr> 
 <tr> 
 <td>fetch.wait.max.ms</td> 
 <td>100</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 fetch.min.bytes.</td> 
 </tr> 
 <tr> 
 <td>rebalance.backoff.ms</td> 
 <td>2000</td> 
 <td>Backoff time between retries during rebalance.</td> 
 </tr> 
 <tr> 
 <td>refresh.leader.backoff.ms</td> 
 <td>200</td> 
 <td>Backoff time to wait before trying to determine the leader of a partition that has just lost its leader.</td> 
 </tr> 
 <tr> 
 <td>auto.offset.reset</td> 
 <td>largest</td> 
 <td>What to do when there is no initial offset in ZooKeeper or if an offset is out of range ;smallest : automatically reset the offset to the smallest offset; largest : automatically reset the offset to the largest offset;anything else: throw exception to the consumer</td> 
 </tr> 
 <tr> 
 <td>consumer.timeout.ms</td> 
 <td>-1</td> 
 <td>若在指定时间内没有消息消费，consumer将会抛出异常。</td> 
 </tr> 
 <tr> 
 <td>exclude.internal.topics</td> 
 <td>true</td> 
 <td>Whether messages from internal topics (such as offsets) should be exposed to the consumer.</td> 
 </tr> 
 <tr> 
 <td>zookeeper.session.timeout.ms</td> 
 <td>6000</td> 
 <td>ZooKeeper session timeout. If the consumer fails to heartbeat to ZooKeeper for this period of time it is considered dead and a rebalance will occur.</td> 
 </tr> 
 <tr> 
 <td>zookeeper.connection.timeout.ms</td> 
 <td>6000</td> 
 <td>The max time that the client waits while establishing a connection to zookeeper.</td> 
 </tr> 
 <tr> 
 <td>zookeeper.sync.time.ms</td> 
 <td>2000</td> 
 <td>How far a ZK follower can be behind a ZK leader</td> 
 </tr> 
 </tbody> 
</table>

参考资料 :尚硅谷大数据

[FzomLj.png]: /images/20220210/1b74b8943c35479da2e48a469e93bf38.png
[FzIAKJ.png]: /images/20220210/9d828143b7f045c781fdc6b9de25c1bc.png
[FzTk7R.png]: /images/20220210/15827caac54347f2943daaac4e8d99f5.png
[Fz7SUI.png]: /images/20220210/75bf23d4ec99488a823e3f0e9dfa1fdb.png
[Fz7GqJ.png]: /images/20220210/9634e34c26ac43299f80317990b17736.png
[FzHkJx.png]: /images/20220210/eb807cbd037644cca4e0173cf8883c65.png
[kSFRxg.png]: /images/20220210/6e9079eff78b49d9beef6167f7ebc2fe.png