centos7搭建kafka单机

虚拟机搭建kafka单机教程

需要安装好java环境

将kafka和zookeeper进行解压,相关目录结构为:

[root@localhost software]# tree -L 1 -C -p kafka/ zookeeper/
kafka/
├── [drwxr-xr-x]  kafka_2.12-2.1.0
└── [-rw-r--r--]  kafka_2.12-2.1.0.tgz
zookeeper/
├── [drwxr-xr-x]  zookeeper-3.4.13
└── [-rw-r--r--]  zookeeper-3.4.13.tar.gz

2 directories, 2 files

配置环境变量,配好的环境变量

# java
export JAVA_HOME=/software/java/jdk1.8.0_202
export CLASSPATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar
export PATH=$PATH:$JAVA_HOME/bin

# scala
export SCALA_HOME=/software/scala/scala-2.12.8
export PATH=$PATH:$SCALA_HOME/bin

# spark
export SPARK_HOME=/software/spark/spark-2.4.0-bin-hadoop2.7
export PATH=$PATH:$SPARK_HOME/bin

# zookeeper
export ZOOKEEPER_HOME=/software/zookeeper/zookeeper-3.4.13
export PATH=$PATH:$ZOOKEEPER_HOME/bin

安装zookeeper|在解压的zookeeper目录下创建data和dataLog目录

# mkdir data dataLog
[root@localhost zookeeper-3.4.13]# ll
total 1712
drwxr-xr-x.  2  501 games    4096 Mar 10 14:08 bin
-rw-r--r--.  1  501 games   91400 Jun 30  2018 build.xml
drwxr-xr-x.  2  501 games      88 Mar 10 14:54 conf
drwxr-xr-x. 10  501 games    4096 Mar 10 14:08 contrib
drwxr-xr-x.  3 root root       60 Mar 10 14:28 data
drwxr-xr-x.  3 root root       22 Mar 10 14:28 dataLog
drwxr-xr-x.  2  501 games    4096 Mar 10 14:08 dist-maven
drwxr-xr-x.  6  501 games    4096 Mar 10 14:08 docs
-rw-r--r--.  1  501 games    1709 Jun 30  2018 ivysettings.xml
-rw-r--r--.  1  501 games    8502 Jun 30  2018 ivy.xml
drwxr-xr-x.  4  501 games    4096 Mar 10 14:08 lib
-rw-r--r--.  1  501 games   11938 Jun 30  2018 LICENSE.txt
-rw-r--r--.  1  501 games    3132 Jun 30  2018 NOTICE.txt
-rw-r--r--.  1  501 games    1585 Jun 30  2018 README.md
-rw-r--r--.  1  501 games    1770 Jun 30  2018 README_packaging.txt
drwxr-xr-x.  5  501 games      44 Mar 10 14:08 recipes
drwxr-xr-x.  8  501 games    4096 Jun 30  2018 src
-rw-r--r--.  1  501 games 1508639 Jun 30  2018 zookeeper-3.4.13.jar
-rw-r--r--.  1  501 games     833 Jul  1  2018 zookeeper-3.4.13.jar.asc
-rw-r--r--.  1  501 games      33 Jun 30  2018 zookeeper-3.4.13.jar.md5
-rw-r--r--.  1  501 games      41 Jun 30  2018 zookeeper-3.4.13.jar.sha1
-rw-r--r--.  1 root root    66288 Mar 10 15:51 zookeeper.out

进入zookeeper的conf目录,复制zoo

# cp zoo_sample.cfg zoo.cfg
[root@localhost zookeeper-3.4.13]# cd conf
[root@localhost conf]# ll
total 16
-rw-r--r--. 1  501 games  535 Jun 30  2018 configuration.xsl
-rw-r--r--. 1  501 games 2161 Jun 30  2018 log4j.properties
-rw-r--r--. 1 root root  1040 Mar 10 14:54 zoo.cfg
-rw-r--r--. 1  501 games  922 Jun 30  2018 zoo_sample.cfg
修改zoo.cfg
[root@localhost conf]# cat 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.
dataDir=/software/zookeeper/zookeeper-3.4.13/data
dataLogDir=/software/zookeeper/zookeeper-3.4.13/dataLog
# 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
server.1=192.168.247.133:2888:3888

进入data目录,新建myid

[root@localhost conf]# cd ../data
[root@localhost data]# ll
total 8
-rw-r--r--. 1 root root 2 Mar 10 14:11 myid
drwxr-xr-x. 2 root root 6 Mar 10 14:28 version-2
-rw-r--r--. 1 root root 4 Mar 10 14:28 zookeeper_server.pid
[root@localhost data]# cat myid
1

启动

[root@localhost zookeeper-3.4.13]# ./bin/zkServer.sh start
ZooKeeper JMX enabled by default
Using config: /software/zookeeper/zookeeper-3.4.13/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED

jps

[root@localhost zookeeper-3.4.13]# jps
4138 Master
8587 QuorumPeerMain
4284 Worker
8605 Jps

安装kafka|在解压目录创建log目录

[root@localhost kafka_2.12-2.1.0]# mkdir log

修改config目录下的server.properties

[root@localhost kafka_2.12-2.1.0]# cd config/
[root@localhost config]# cat server.properties 
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#    http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# see kafka.server.KafkaConfig for additional details and defaults

############################# Server Basics #############################

# 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
listeners=PLAINTEXT://192.168.247.133: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.dirs=/software/kafka/kafka_2.12-2.1.0/log

# 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 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.connect=192.168.247.133: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,并jps查看

[root@localhost kafka_2.12-2.1.0]# ./bin/kafka-server-start.sh -daemon ./config/server.properties
[root@localhost kafka_2.12-2.1.0]# jps
9909 Jps
9878 Kafka
4138 Master
8587 QuorumPeerMain
4284 Worker
[root@localhost conf]# netstat -tunlp|egrep "(2181|9092)"
tcp6       0      0 192.168.247.133:9092    :::*                    LISTEN      9878/java           
tcp6       0      0 :::2181                 :::*                    LISTEN      8587/java

创建topic

[root@localhost config]# bin/kafka-topics.sh --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic test

生产消息

# bin/kafka-console-producer.sh --broker-list 192.168.247.133:9092 --topic test

消费消息

[root@localhost kafka_2.12-2.1.0]# ./bin/kafka-console-consumer.sh --bootstrap-server 192.168.247.133:9092 --topic test --from-beginning
test
test
test
test
tset
^CProcessed a total of 5 messages

拾柒……

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值