JDK 版本 1.7

使用命令解压 文件

tar -zxvf kafka_2.12-2.3.0.tgz

修改配置文件

[julong@localhost ~]$ cd kafka_2.12-2.3.0/
[julong@localhost kafka_2.12-2.3.0]$ ls
bin config libs LICENSE logs NOTICE site-docs
[julong@localhost kafka_2.12-2.3.0]$ cd config/
[julong@localhost config]$ pwd
/home/julong/kafka_2.12-2.3.0/config
[julong@localhost config]$ ls
connect-console-sink.properties connect-distributed.properties connect-file-source.properties connect-standalone.properties log4j.properties server.properties trogdor.conf
connect-console-source.properties connect-file-sink.properties connect-log4j.properties consumer.properties producer.properties tools-log4j.properties zookeeper.properties
[julong@localhost config]$

zookeeper.properties 对应自己的zookeeper 如果自己安装过zookeeper 可以忽略此步骤

[julong@localhost config]$ vim zookeeper.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.
# the directory where the snapshot is stored.
dataDir=/tmp/zookeeper
# the port at which the clients will connect
clientPort=2181
# disable the per-ip limit on the number of connections since this is a non-production config
maxClientCnxns=0

server.properties

[julong@localhost config]$ vim 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 监听地址 这一块儿建议不要使用 localhost 如果使用 localhost 到时候使用程序调用的时候 是无法创建消息的 ,我测试过的。
listeners=PLAINTEXT://192.168.10.222: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=/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 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 地址
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

启动服务:

启动中如果加入 -daemon 为以守护进程的方式后台启动命令 如果不加入 则前台启动

[julong@localhost kafka_2.12-2.3.0]$ bin/kafka-server-start.sh -daemon config/server.properties 
[julong@localhost kafka_2.12-2.3.0]$ ps -aux|grep kafka
julong 123679 79.1 19.6 4734324 367324 pts/1 Sl 13:41 0:07 /usr/etc/jdk1.8.0_45/bin/java -Xmx1G -Xms1G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 -XX:+ExplicitGCInvokesConcurrent -Djava.awt.headless=true -Xloggc:/home/julong/kafka_2.12-2.3.0/bin/../logs/kafkaServer-gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=100M -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dkafka.logs.dir=/home/julong/kafka_2.12-2.3.0/bin/../logs -Dlog4j.configuration=file:bin/../config/log4j.properties -cp .:/usr/etc/jdk1.8.0_45/lib:/usr/etc/jdk1.8.0_45/jre/lib:/home/julong/kafka_2.12-2.3.0/bin/../libs/activation-1.1.1.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/aopalliance-repackaged-2.5.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/argparse4j-0.7.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/audience-annotations-0.5.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/commons-lang3-3.8.1.jar:/home/julongkafka_2.12-2.3.0/bin/../libs/connect-api-2.3.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/connect-basic-auth-extension-2.3.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/connect-file-2.3.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/connect-json-2.3.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/connect-runtime-2.3.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/connect-transforms-2.3.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/guava-20.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/hk2-api-2.5.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/hk2-locator-2.5.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/hk2-utils-2.5.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-annotations-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-core-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-databind-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-dataformat-csv-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-datatype-jdk8-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-jaxrs-base-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-jaxrs-json-provider-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-module-jaxb-annotations-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-module-paranamer-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jackson-module-scala_2.12-2.9.9.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jakarta.annotation-api-1.3.4.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jakarta.inject-2.5.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jakarta.ws.rs-api-2.1.5.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/javassist-3.22.0-CR2.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/javax.servlet-api-3.1.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/javax.ws.rs-api-2.1.1.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jaxb-api-2.3.0.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jersey-client-2.28.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jersey-common-2.28.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jersey-container-servlet-2.28.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jersey-container-servlet-core-2.28.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jersey-hk2-2.28.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jersey-media-jaxb-2.28.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jersey-server-2.28.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jetty-client-9.4.18.v20190429.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jetty-continuation-9.4.18.v20190429.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jetty-http-9.4.18.v20190429.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jetty-io-9.4.18.v20190429.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jetty-security-9.4.18.v20190429.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jetty-server-9.4.18.v20190429.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jetty-servlet-9.4.18.v20190429.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jetty-servlets-9.4.18.v20190429.jar:/home/julong/kafka_2.12-2.3.0/bin/../libs/jetty-util-9.4.18.v20190429.jar:
julong 123753 0.0 0.0 112812 976 pts/1 S+ 13:41 0:00 grep --color=auto kafka

创建主题:

### 创建主题 
[julong@localhost bin]$ ./kafka-topics.sh --create --bootstrap-server 192.168.10.222:9092 --replication-factor 1 --partitions 1 --topic test-001

### 查看主题创建的列表
[julong@localhost bin]$ ./kafka-topics.sh --list --bootstrap-server 192.168.10.222:9092
__consumer_offsets
julong-test
test
test-001
[julong@localhost bin]$

本机测试消息发送 重新开连个 窗口

### 生产者 消息创建方 控制台创建消息 
bin/kafka-console-producer.sh --broker-list 192.168.10.222:9092 --topic test-001
>julong
>

消息接收:

bin/kafka-console-consumer.sh --bootstrap-server 192.168.10.222:9092 --topic test-001 --from-beginning
[2021-11-20 14:33:22,726] WARN [Consumer clientId=consumer-1, groupId=console-consumer-24410] Error while fetching metadata with correlation id 2 : {test-001=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
julong

至此 kafka 基本使用环境

搭建完成