1. 集群配置
1.1 配置Zookeeper集群
- 因为当前版本的Kafka强依赖于Zookeeper,先创建Zookeeper集群
# 下载Zokeeper
wget https://archive.apache.org/dist/zookeeper/zookeeper-3.7.1/apache-zookeeper-3.7.1-bin.tar.gz
# 解压zookeeper到/opt/zokeeper
mkdir /opt/zookeeper
tar -zxvf apache-zookeeper-3.7.1-bin.tar.gz -C /opt/zokeeper
# 复制三份Zookeeper, 并复制zoo.cfg
cd /opt/zookeeper
cp -rf apache-zookeeper-3.7.1-bin ./zookeeper-01
cd zookeeper-01/conf
cp -rf zoo_sample.cfg ./zoo.cfg
cd ../../
cp -rf zookeeper-01 ./zookeeper-02
cp -rf zookeeper-01 ./zookeeper-03
# 修改每个zookeeper的配置文件
vim zookeeper-01/conf/zoo.cfg
vim zookeeper-02/conf/zoo.cfg
vim zookeeper-03/conf/zoo.cfg
# 修改详细
# 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.
# 加上data目录和log目录
dataDir=/opt/zookeeper/zookeeper-01/data
dataLogDir=/opt/zookeeper/zookeeper-01/log
# 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
# 添加你服务器节点的IP、端口、代理端口
server.0=IP1:2888:3888
server.1=IP2:2889:3889
server.2=IP3:2890:3890
## Metrics Providers
#
# https://prometheus.io Metrics Exporter
#metricsProvider.className=org.apache.zookeeper.metrics.prometheus.PrometheusMetricsProvider
#metricsProvider.httpPort=7000
#metricsProvider.exportJvmInfo=true
# 在每个zookeeper的data目录中添加myid, 每个zookeeper的myid都需要不一样,要和zoo.cfg中的服务器配置一致
vim zookeeper-01/data/myid
vim zookeeper-02/data/myid
vim zookeeper-03/data/myid
- 我这里设置zookeeper-01的clientPort=2181,zookeeper-02的clientPort=2182,zookeeper-03的clientPort=2183
- 记住,多少个zookeeper就要写多少个服务器节点的IP、端口、代理端口
# 启动三个zookeeper
zookeeper-01/bin/zkServer.sh start
zookeeper-02/bin/zkServer.sh start
zookeeper-03/bin/zkServer.sh start
# 可以查看zookeeper的状态
zookeeper-01/bin/zkServer.sh status
zookeeper-02/bin/zkServer.sh status
zookeeper-03/bin/zkServer.sh status
1.2 配置Kafka集群
# 下载Kafka
wget https://archive.apache.org/dist/kafka/2.4.1/kafka_2.11-2.4.1.tgz
# 解压kafka安装到/opt/kafka
tar -xzf kafka_2.11-2.4.1.tgz -C /opt/kafka
cd /opt/kafka
# 复制三份kafka
cp -rf kafka_2.11-2.4.1 ./kafka-01
cp -rf kafka-01 ./kafka-02
cp -rf kafka-01 ./kafka-03
# 更改每个kafka的配置
vim kafka-01/config/server.properties
vim kafka-02/config/server.properties
vim kafka-03/config/server.properties
# 编辑细节
############################# Server Basics #############################
# The id of the broker. This must be set to a unique integer for each broker.
# 这个id必须是唯一的
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
# 添加你kafka服务器的IP地址和端口号在这里
listeners=PLAINTEXT://your.host.name: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
# 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 separated list of directories under which to store log files
# 添加log目录路径
log.dirs=/opt/kafka/kafka-01/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 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 excessive 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集群ip和端口号, 用','隔开
zookeeper.connect=IP1:2181,IP2:2182,IP3:2183
# 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服务
kafka-01/bin/kafka-server-start.sh start
kafka-02/bin/kafka-server-start.sh start
kafka-03/bin/kafka-server-start.sh start
# 查看java程序进程
jps
# 显示的进程
96883 Kafka
96066 Kafka
10503 QuorumPeerMain
10138 QuorumPeerMain
93885 Kafka
11277 QuorumPeerMain
97999 Jps
# 已有三个Kafka和三个QuorumPeerMain, Kafka集群已经开启成功
2.测试
2.1. JavaApi测试
- 发送message的时候一定要注意topic一致
# yml配置文件
server:
port: xxx
spring:
kafka:
bootstrap-servers: IP1:9092,IP1:9093,IP1:9094 # kafka的服务IP和端口号, 用','隔开
producer: # producer 生产者
retries: 0 # 重试次数
acks: 1 # 应答级别:多少个分区副本备份完成时向生产者发送ack确认(可选0、1、all/-1)
batch-size: 16384 # 批量大小
buffer-memory: 33554432 # 生产端缓冲区大小
key-serializer: org.apache.kafka.common.serialization.StringSerializer
value-serializer: org.apache.kafka.common.serialization.StringSerializer
consumer: # consumer消费者
group-id: XXXgroup # 默认的消费组ID
enable-auto-commit: true # 是否自动提交offset
auto-commit-interval: 100 # 提交offset延时(接收到消息后多久提交offset)
# earliest:当各分区下有已提交的offset时,从提交的offset开始消费;无提交的offset时,从头开始消费
# latest:当各分区下有已提交的offset时,从提交的offset开始消费;无提交的offset时,消费新产生的该分区下的数据
# none:topic各分区都存在已提交的offset时,从offset后开始消费;只要有一个分区不存在已提交的offset,则抛出异常
auto-offset-reset: latest
key-deserializer: org.apache.kafka.common.serialization.StringDeserializer
value-deserializer: org.apache.kafka.common.serialization.StringDeserializer
// KafkaProducer.java, 发送
@RestController
public class KafkaProducer {
@Resource
private KafkaTemplate<String, Object> kafkaTemplate;
@PostMapping("/kafka/send")
public void sendMessage(MqDto msg) {
MqDto message = new MqDto();
BeanUtils.copyProperties(msg, message);
kafkaTemplate.send(Constants.TOPICS, JSON.toJSONString(message));
}
}
// KafkaConsumer.java, 获取
@Component
@Slf4j
public class KafkaConsumer {
@KafkaListener(topics = {Constants.TOPICS}, groupId = Constants.GROUP)
public void onMessage1(ConsumerRecord<?, ?> consumerRecord) {
Optional<?> optional = Optional.ofNullable(consumerRecord.value());
if (optional.isPresent()) {
Object msg = optional.get();
log.info("message:{}", msg);
}
}
}
2.2.在服务器中测试
- 也可以自己在服务器上自己创建消费者进行测试,记住一定要开启了kafka服务才开始创建消费者
bin/kafka-console-consumer.sh --bootstrap-server IP:9092,IP:9093,IP:9094 --from-beginning --topic YOURTOPIC