1############################# 服务基本设置 ############################# 2 3# The id of the broker. This must be set to a unique integer for each broker. 4# kafka集群分组ID 5broker.id=1 6 7############################# Socket Server 设置 ############################# 8 9listeners=PLAINTEXT://:9092 10 11# socket服务监听端口号 12port=9092 13 14# 主机名 15host.name=192.168.30.65 16 17# Hostname the broker will advertise to producers and consumers. If not set, it uses the 18# value for "host.name" if configured. Otherwise, it will use the value returned from 19# java.net.InetAddress.getCanonicalHostName(). 20advertised.host.name=192.168.30.65 21 22# The port to publish to ZooKeeper for clients to use. If this is not set, 23# it will publish the same port that the broker binds to. 24#advertised.port=<port accessible by clients> 25 26# 处理网络请求的线程数 27num.network.threads=3 28 29# 处理磁盘I/O的线程数 30num.io.threads=8 31 32# socket传输数据大小 33socket.send.buffer.bytes=102400 34 35# socket接收数据大小 36socket.receive.buffer.bytes=102400 37 38# socket最大请求字节数 39socket.request.max.bytes=104857600 40 41 42############################# 日志配置 ############################# 43 44# 日志存放目录 45log.dirs=/u01/kafka/kafka-logs 46 47# 分区大小. 48num.partitions=3 49 50# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown. 51# This value is recommended to be increased for installations with data dirs located in RAID array. 52num.recovery.threads.per.data.dir=1 53 54"server.properties" [只读] 137L, 6294C 1,1 顶端 55num.recovery.threads.per.data.dir=1 56 57############################# Log Flush Policy ############################# 58 59# Messages are immediately written to the filesystem but by default we only fsync() to sync 60# the OS cache lazily. The following configurations control the flush of data to disk. 61# There are a few important trade-offs here: 62# 1. Durability: Unflushed data may be lost if you are not using replication. 63# 2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush. 64# 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to exceessive seeks. 65# The settings below allow one to configure the flush policy to flush data after a period of time or 66# every N messages (or both). This can be done globally and overridden on a per-topic basis. 67 68# The number of messages to accept before forcing a flush of data to disk 69#log.flush.interval.messages=10000 70 71# The maximum amount of time a message can sit in a log before we force a flush 72#log.flush.interval.ms=1000 73 74############################# 日志存储策略 ############################# 75 76# 当达到下面的消息数量时,会将数据flush到日志文件中。默认10000 77**log.flush.interval.messages=10000 78**# 当达到下面的时间(ms)时,执行一次强制的flush操作。interval.ms和interval.messages无论哪个达到,都会flush。默认3000ms 79**log.flush.interval.ms=1000** 80# 检查是否需要将日志flush的时间间隔 81**log.flush.scheduler.interval.ms=3000** 82# 日志保存时间 (hours|minutes),默认为7天(168小时)。超过这个时间会根据policy处理数据。bytes和minutes无论哪个先达到都会触发。 83**log.retention.hours=24** 84# 日志数据存储的最大字节数。超过这个时间会根据policy处理数据。 85**log.retention.bytes=21474836480** 86 87# 控制日志segment文件的大小,超出该大小则追加到一个新的日志segment文件中(-1表示没有限制) 88**log.segment.bytes=1073741824** 89# 当达到下面时间,会强制新建一个segment 90**log.roll.hours=168** 91# 日志片段文件的检查周期,查看它们是否达到了删除策略的设置(log.retention.hours或log.retention.bytes) 92**log.retention.check.interval.ms=60000** 93 94# 是否开启压缩 95**log.cleaner.enable=false** 96# 日志清理策略(delete|compact) 97**log.cleanup.policy=delete** 98# 对于压缩的日志保留的最长时间 99**log.cleaner.delete.retention.ms=86400000** 100 101# 对于segment日志的索引文件大小限制 102**log.index.size.max.bytes=10485760** 103#y索引计算的一个缓冲区,一般不需要设置。 104**log.index.interval.bytes=4096** 105 106############################# Zookeeper配置 ############################# 107 108# zookeeper节点 109#zookeeper.connect=192.168.30.65:2188,192.168.30.66:2188,192.168.30.67:2188 110**zookeeper.connect=192.168.30.65:2188** 111 112# zookeeper网络连接超时时间 113**zookeeper.connection.timeout.ms=6000 **
Kafka配置文件
Stella981
2021-10-11
1122 0 0
点赞
收藏
评论区
加载中...