zookeeper和kafka安装

介绍zookeeper和kafka安装

一、安装zookeeper

参考链接
https://www.cnblogs.com/lsdb/p/7297731.html
先去官网下载zk
1、解压
tar -zxvf zookeeper-3.4.9.tar.gz
2、在主目录下创建data和logs两个目录用于存储数据和日志
3、进入conf,把zoo_sample.cfg 拷贝成zoo.cfg,修改配置

tickTime=2000
initLimit=10
syncLimit=5

dataDir=/data/zookeeper/zookeeper-3.4.9/data
dataLogDir=/data/zookeeper/zookeeper-3.4.9/logs
clientPort=2181

#集群配置，单机不需要配置下面
server.1=172.18.144.210:2888:3888
server.2=192.168.220.129:2888:3888

4、集群还需如下配置
在data目录下建myid，值1，其它服务器值依次加

5、启动和停止
进入bin目录，启动、停止、重启分和查看当前节点状态（包括集群中是何角色）别执行：

./zkServer.sh start
./zkServer.sh stop
./zkServer.sh restart
./zkServer.sh status

二、kafka安装

参考
https://blog.csdn.net/weixin_42575806/article/details/80981743
1.解压 tar -zxvf kafka_2.12-0.10.2.0.tgz
2、修改配置文件server.properties

#另一台服务器值不一样
broker.id=1

# Switch to enable topic deletion or not, default value is false
delete.topic.enable=true

############################# 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
host.name=119.23.235.192
# 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

listeners=PLAINTEXT://172.18.144.210:9092
advertised.listeners=PLAINTEXT://119.23.235.192:9092
advertised.host.name=119.23.235.192

# 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 handling network requests
num.network.threads=3

# The number of threads doing 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=/data/kafka/kafka_2.12-0.10.2.0/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

############################# 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 as long as the remaining
# segments don't 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.connect=119.23.235.192:2181,119.23.39.184:2181

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000

3、运行kafka
./bin/kafka-server-start.sh -daemon config/server.properties

#创建一个test主题，分区数为2,备份数为2
#在kafka根目录执行下面命令
./bin/kafka-topics.sh --create --zookeeper 119.23.235.192:2181 --replication-factor 2 --partitions 2 --topic test
#kafka根目录执行，启动一个生产者
./bin/kafka-console-producer.sh --broker-list 119.23.235.192:9092 --topic test
#启动消费者命令
./bin/kafka-console-consumer.sh --zookeeper 119.23.235.192:2181 --topic test --from-beginning