linux下Kafka安装及基本操作

1.下载Kafka

http://archive.apache.org/dist/kafka/1.1.0/

2.解压并重命名

mkdir /usr/local/kafka
cd /usr/local
tar zxvf kafka_2.12-1.1.0.tgz
mv kafka_2.12-1.1.0  ./kafka   //把kafka_2.12-1.1.0下的文件拷贝到/usr/local/kafka下面

3.配置kafka

mkdir /usr/local/kafka/log/kafka #创建kafka日志目录
cd /usr/local/kafka/config #进入配置目录
vi server.properties #编辑修改相应的参数
broker.id=0
port=9092 #端口号
host.name=hostname #hostname
listeners=PLAINTEXT://hostname:9092
log.dirs=/usr/local/kafka/log/kafka #日志存放路径,上面创建的目录
zookeeper.connect=localhost:2181 #zookeeper地址和端口,单机配置部署,localhost:2181

文件目录在 /usr/local/config/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

# 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.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


port=9092
host.name=localhost
listeners=PLAINTEXT://localhost:9092
log.dirs=/usr/local/kafka/log/kafka
zookeeper.connect=localhost:2181

4.配置zookeeper

mkdir /usr/local/kafka/zookeeper #创建zookeeper目录
mkdir /usr/local/kafka/log/zookeeper #创建zookeeper日志目录
cd /usr/local/kafka/config #进入配置目录
vi zookeeper.properties #编辑修改相应的参数
dataDir=/usr/local/kafka/zookeeper #zookeeper数据目录
dataLogDir=/usr/local/kafka/log/zookeeper #zookeeper日志目录
clientPort=2181
maxClientCnxns=100
tickTime=2000
initLimit=10
syncLimit=5

文件目录在 /usr/local/config/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

dataDir=/usr/local/kafka/zookeeper
dataLogDir=/usr/local/kafka/log/zookeeper
clientPort=2181
maxClientCnxns=100
tickTime=2000
initLimit=10
syncLimit=5


5.启动脚本(自己创建)

文件目录在 /usr/local/kafka/bin/kafkastart.sh


keeper
/usr/local/kafka/bin/zookeeper-server-start.sh /usr/local/kafka/config/zookeeper.properties &

sleep 3   #等3秒后执行

#启动kafka
/usr/local/kafka/bin/kafka-server-start.sh /usr/local/kafka/config/server.properties &

6.停止脚本

文件目录在 /usr/local/kafka/bin/kafkastop.sh


keeper
/usr/local/kafka/bin/zookeeper-server-stop.sh /usr/local/kafka/config/zookeeper.properties &

sleep 3 #等3秒后执行

#关闭kafka
/usr/local/kafka/bin/kafka-server-stop.sh /usr/local/kafka/config/server.properties &

7.创建一个Topic

bin/kafka-topics.sh --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic test

8.查看Topic

bin/kafka-topics.sh --list --zookeeper localhost:2181

9.发送消息

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

10.消费消息

bin/kafka-console-consumer.sh --bootstrap-server hostname:9092 --topic test --from-beginning

  • 9
    点赞
  • 6
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
### 回答1: 安装Kafka集群的步骤如下: 1. 下载Kafka安装包并解压缩到指定目录。 2. 配置Kafka集群的Zookeeper服务,可以使用已有的Zookeeper集群或者单独安装一个Zookeeper集群。 3. 配置Kafka集群的Broker节点,包括修改配置文件、启动Broker进程等。 4. 配置Kafka集群的Topic,包括创建Topic、修改Topic配置等。 5. 测试Kafka集群的功能,包括发送和接收消息等。 以上是Kafka集群的基本安装步骤,具体操作可以参考Kafka官方文档或者相关教程。 ### 回答2: Kafka是一个分布式的消息队列系统,可以支持大规模的消息处理和存储。在Linux系统中安装Kafka集群一般需要以下步骤: 1. 首先安装Java环境,因为Kafka是用Java语言编写的,需要在Linux系统中安装Java环境,可以通过在终端执行命令sudo apt-get install openjdk-8-jdk来安装。 2. 下载Kafka压缩包,可以从Kafka官网下载最新版本的压缩包。 3. 解压Kafka压缩包,可以将下载的Kafka压缩包解压到指定目录下,并设置好环境变量,方便后续的操作。 4. 配置Kafka集群的broker,可以在Kafka的配置文件server.properties中配置Kafka broker的参数和属性,比如端口号、存储路径、日志目录等。 5. 配置Kafka集群的Zookeeper,Zookeeper是Kafka集群中必不可少的一部分,需要在配置文件zookeeper.properties中设置Zookeeper集群的参数和属性,比如端口号、数据目录等。 6. 启动Kafka集群,在终端中输入命令bin/kafka-server-start.sh config/server.properties启动Kafka集群,然后再输入命令bin/kafka-topics.sh等其他命令,可以进行一些测试和操作。 7. 部署Kafka集群的生产环境,需要对Kafka集群进行一些性能调优和安全配置,防止出现安全漏洞和性能问题。 总之,安装Kafka集群需要一定的技术基础和经验,需要注意配置文件的编写和参数的设置,同时需要对Kafka集群进行性能调优和安全配置。 ### 回答3: Kafka是一个高性能、高吞吐量、分布式的消息系统,广泛应用于大数据场景下的数据处理与分析。要想在Linux系统上安装Kafka集群,我们需要按照以下步骤进行操作: 1. 首先,我们需要在所有节点上安装Java环境,并确保Java版本不低于Java8。可以使用以下命令进行安装: sudo apt-get update sudo apt-get install default-jdk 2. 接着,我们需要下载并解压Kafka的二进制安装包。可以从官方网站上下载最新版本的Kafka:https://kafka.apache.org/downloads。下载完成后解压到指定目录,例如: tar -xzf kafka_2.12-2.5.0.tgz cd kafka_2.12-2.5.0 3. 在Kafka集群中,我们需要至少创建两个节点,一个节点充当生产者,另一个节点充当消费者。在每个节点上,我们需要创建一个配置文件来指定Broker的ID、主机名、监听端口等参数。 例如,在节点1上创建配置文件: vi config/server.properties 添加以下内容: broker.id=1 listeners=PLAINTEXT://hostname1:9092 advertised.listeners=PLAINTEXT://<public_hostname>:9092 log.dirs=/tmp/kafka-logs 其中,broker.id代表当前节点的唯一标识,listeners和advertised.listeners分别指定了当前节点的监听地址和对外广告地址,log.dirs指定了日志文件存放路径。 在节点2上创建类似的配置文件,但是broker.id和listeners需要设置成不同的值。 4. 在所有节点上启动Zookeeper服务器。因为Kafka集群使用Zookeeper来管理Broker节点的状态。我们可以在一个节点上启动单独的Zookeeper服务器,也可以在所有节点上启动Zookeeper集群。 在单独一个节点上启动Zookeeper服务器: ./bin/zookeeper-server-start.sh config/zookeeper.properties 在所有节点上启动Zookeeper集群: ./bin/zookeeper-server-start.sh config/zookeeper.properties 5. 在每个节点上启动Kafka Broker。我们可以使用以下命令来启动Kafka Broker: ./bin/kafka-server-start.sh config/server.properties 请注意,在启动Kafka Broker之前,我们需要确保当前节点的Zookeeper服务器已经启动,并且所有Broker的配置文件中都指定了正确的Zookeeper地址。 6. 现在,我们已经成功地在所有节点上启动了Kafka Broker。我们可以使用Kafka提供的命令行工具来创建Topic、发送消息和消费消息等操作。例如,创建一个名为test的Topic: ./bin/kafka-topics.sh --create --zookeeper <zookeeper_host>:<zookeeper_port> --replication-factor 2 --partitions 4 --topic test 其中,--replication-factor参数指定了每个Partition的副本数,使用Even交换策略时,建议将--replication-factor设为节点数的一半,或不小于3。 7. 最后,我们可以在生产者节点上使用以下命令来发送消息: ./bin/kafka-console-producer.sh --broker-list <broker1>:9092,<broker2>:9092 --topic test 在消费者节点上使用以下命令来消费消息: ./bin/kafka-console-consumer.sh --bootstrap-server <broker1>:9092,<broker2>:9092 --topic test --from-beginning 以上是在Linux系统上安装Kafka集群的一般步骤。当然,对于特定的应用场景和业务要求,具体的配置和调整可能会不同。需要根据实际情况进行调整和优化。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值