一:相对于rabbitMQ,kafka功能更强大,更稳定。介绍kafka什么的都省了,推荐一个https://blog.csdn.net/tangdong3415/article/details/53432166。
二:kafka安装,可以安装windows版本或者Linux版本,个人建议安装Linux版本的,比较稳定,windows版本的不好控制。
1.kafka依赖于Zookeeper,安装kafka需要安装Zookeeper,kafka自带有Zookeeper,个人建议自己安装Zookeeper,Zookeeper依赖JDK,建议安装JDK1.8以上版本。
JDK官网下载:http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
JDK安装自行百度
zookeeper官网下载地址:https://www.apache.org/dyn/closer.cgi/zookeeper/
kafka网下载地址:http://kafka.apache.org/downloads.html
2.下载完成后放到Linux下解压安装即可。
解压命令:tar -zxvf tar包名称
解压完成即可。
二:配置zookeeper和kafka
PS:这里多说一点,避免大家跳坑,如果是在虚拟机上安装,1:先把防火墙关掉,不然从外部连接会连接不上。2:kafka配置文件中的 listeners = PLAINTEXT://192.168.169.128:9092和advertised.listeners=PLAINTEXT://192.168.169.128:9092一定配的是请求的端口,不然也会从外部连接不上。
1.解压完成后进入zookeeper相应目录,进入conf目录,拷贝zoo_sample.cfg 为zoo.cfg
2.大概配置如下
# The number of milliseconds of each tick
tickTime=2000
# The number of ticks that the initial
# synchronization phase can take
initLimit=10
# The number of ticks that can pass between
# sending a request and getting an acknowledgement
syncLimit=5
# the directory where the snapshot is stored.
# do not use /tmp for storage, /tmp here is just
# example sakes.自己在zookeeper相应目录建立一个文件夹,存放的是日志文件
dataDir=/opt/zookeeper-3.4.12/dataDir
# the port at which the clients will connect默认端口
clientPort=2181
# the maximum number of client connections.
# increase this if you need to handle more clients
#maxClientCnxns=60
#
# Be sure to read the maintenance section of the
# administrator guide before turning on autopurge.
#
# http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance
#
# The number of snapshots to retain in dataDir
#autopurge.snapRetainCount=3
# Purge task interval in hours
# Set to "0" to disable auto purge feature
#autopurge.purgeInterval=1
3.配置kafka,进入相应目录。
# see kafka.server.KafkaConfig for additional details and defaults
############################# Server Basics #############################
# 服务id ,唯一不能重复The id of the broker. This must be set to a unique integer for each broker.
broker.id=0
############################# Socket Server Settings #############################
# The address the socket server listens on. It will get the value returned from
# java.net.InetAddress.getCanonicalHostName() if not configured.
# FORMAT:
# listeners = listener_name://host_name:port
# EXAMPLE:
# listeners = PLAINTEXT://your.host.name:9092
#listeners=PLAINTEXT://:9092
#监听请求的ip和端口,下同
listeners = PLAINTEXT://192.168.169.128:9092
# Hostname and port the broker will advertise to producers and consumers. If not set,
# it uses the value for "listeners" if configured. Otherwise, it will use the value
# returned from java.net.InetAddress.getCanonicalHostName().
#advertised.listeners=PLAINTEXT://your.host.name:9092
advertised.listeners=PLAINTEXT://192.168.169.128:9092
# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL
# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3
# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=8
# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=102400
# The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes=102400
# The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes=104857600
############################# Log Basics #############################
# A comma seperated list of directories under which to store log files
log.dirs=/tmp/kafka-logs
# The default number of log partitions per topic. More partitions allow greater
# parallelism for consumption, but this will also result in more files across
# the brokers.
num.partitions=1
# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
# This value is recommended to be increased for installations with data dirs located in RAID array.
num.recovery.threads.per.data.dir=1
############################# Internal Topic Settings #############################
# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
# For anything other than development testing, a value greater than 1 is recommended for to ensure availability such as 3.
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=1
############################# Log Flush Policy #############################
# Messages are immediately written to the filesystem but by default we only fsync() to sync
# the OS cache lazily. The following configurations control the flush of data to disk.
# There are a few important trade-offs here:
# 1. Durability: Unflushed data may be lost if you are not using replication.
# 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.
# 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to exceessive seeks.
# The settings below allow one to configure the flush policy to flush data after a period of time or
# every N messages (or both). This can be done globally and overridden on a per-topic basis.
# The number of messages to accept before forcing a flush of data to disk
#log.flush.interval.messages=10000
# The maximum amount of time a message can sit in a log before we force a flush
#log.flush.interval.ms=1000
############################# Log Retention Policy #############################
# The following configurations control the disposal of log segments. The policy can
# be set to delete segments after a period of time, or after a given size has accumulated.
# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens
# from the end of the log.
# The minimum age of a log file to be eligible for deletion due to age
#日志存放期限,超过就删除,一般是一周
log.retention.hours=168
# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
#log.retention.bytes=1073741824
# The maximum size of a log segment file. When this size is reached a new log segment will be created.
log.segment.bytes=1073741824
# The interval at which log segments are checked to see if they can be deleted according
# to the retention policies
log.retention.check.interval.ms=300000
############################# Zookeeper #############################
# Zookeeper connection string (see zookeeper docs for details).
# This is a comma separated host:port pairs, each corresponding to a zk
# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
# You can also append an optional chroot string to the urls to specify the
# root directory for all kafka znodes.
#配置zookeeper地址和端口
zookeeper.connect=localhost:2181
# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000
############################# Group Coordinator Settings #############################
# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
# The default value for this is 3 seconds.
# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup.
group.initial.rebalance.delay.ms=0
#自建文件夹,存放kafka启动日志
log.dir=/opt/hezhihua/kafka_2.11-1.0.1/logs
需要配置的基本就几个
kafka服务配置文件
启用删除策略
log.cleanup.policy=delete
##日志保留日期设置的是7天
log.retention.hours=168
# 定时检查周期,发现数据存了超过上面配置的时间,就干数据
log.retention.check.interval.ms=300000
超过指定大小后,删除旧的消息:
log.retention.bytes=1073741824
## 是否开启日志压缩
log.cleaner.enable=false
log.cleanup.policy=compact 启用压缩策略
#删除topic权限开启
delete.topic.enable=true
超过指定大小后,删除旧的消息:
log.retention.bytes=1073741824
三:启动验证。Linux centos7版本
1.zookeeper命令:
1. 启动ZK服务: sh bin/zkServer.sh start
2. 查看ZK服务状态: bin/zkServer.sh status
3. 停止ZK服务: sh bin/zkServer.sh stop
4. 重启ZK服务: sh bin/zkServer.sh restart
2.kafka命令:
1.kafka启动命令:
bin/kafka-server-start.sh config/server.properties &
2.kafka关闭命令
bin/kafka-server-stop.sh config/server.properties &
3.运行 producer:
bin/kafka-console-producer.sh --broker-list localhost:9092 --topic 主题名称
4.运行 consumer:
bin/kafka-console-consumer.sh --zookeeper localhost:2181 --topic 主体名称 --from-beginning
5.查看topic列表
bin/kafka-topics.sh --list --zookeeper localhost:2181
四:如果没有意外,在生产者端发送消息,消费端会收到消息。那么恭喜你安装成功。
希望能帮到大家,下节讲Java整合kafka操作。