美文网首页
Kafka_2.11_0.9.0.1集群搭建

Kafka_2.11_0.9.0.1集群搭建

作者: 陪你一起debug | 来源:发表于2018-12-05 18:00 被阅读0次

1.版本

  • system: windows10
  • jdk: 1.8.0_141
  • zookeeper: 3.4.10
  • kafka: 2.11-0.9.0.1

2.安装

  • 安装zookeeper3.4.10集群,可参考https://www.jianshu.com/p/ae688aa142d1
    tar -zvxf kafka_2.11-0.9.0.1.tar.gz解压
    cd kafka_2.11-0.9.0.1进入安装目录
    mkdir log建立日志目录
    vim 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.
# 集群机器标识,另外两台为1,2
broker.id=1 

############################# Socket Server Settings #############################

# 当前机器的地址
listeners=PLAINTEXT://100.124.21.1:9092

# The port the socket server listens on
# 监听端口
port=9092

# Hostname the broker will bind to. If not set, the server will bind to all interfaces
# 当前机器的地址
host.name=100.124.21.1

# Hostname the broker will advertise to producers and consumers. If not set, it uses the
# value for "host.name" if configured.  Otherwise, it will use the value returned from
# java.net.InetAddress.getCanonicalHostName().
#advertised.host.name=<hostname routable by clients>

# The port to publish to ZooKeeper for clients to use. If this is not set,
# it will publish the same port that the broker binds to.
#advertised.port=<port accessible by clients>

# 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=/usr/local/kafka_2.11-0.9.0.1/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

############################# 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
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.
#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=100.21.21.1:2181,100.124.21.2:2181,100.124.21.4:2181/kafka

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

scp -r /usr/local/kafka_2.11-0.9.0.1 ip:/usr/local拷贝到另外两台机器修改配置文件中的ipzookeeper连接信息

3.启动

分别进入三台机器bin目录下,执行./kafka-server-start.sh -daemon ../config/server.properties启动
jps查看kafka进程

kafka进程

4.测试

  • ./kafka-topics.sh --create --zookeeper 100.124.21.1:2181/kafka --replication-factor 1 --partitions 1 --topic test创建主题
  • ./kafka-topics.sh --list --zookeeper 100.124.21.1:2181查看创建的主题
  • ./kafka-console-consumer.sh --topic test --from-beginning --zookeeper 100.124.21.1:2181/kafka监听创建的主题
  • ./kafka-console-producer.sh --broker-list 100.124.21.1:90 --topic test发送消息,输入hello world回车即发送成功
    kafka发送数据
kafka接收数据,上面的是之前测试接受的

相关文章

网友评论

      本文标题:Kafka_2.11_0.9.0.1集群搭建

      本文链接:https://www.haomeiwen.com/subject/qnmwcqtx.html