一、下載地址：
鏈接: https://pan.baidu.com/s/18vp_qCGZgZNjtaewOCc3Uw
密碼:54jh
二、啓動zookeeper：
[root@javaxiaobang kafka]# bin/zookeeper-server-start.sh config/zookeeper.properties > zookeeper.log &
[1] 4232
[root@javaxiaobang kafka]#
三、配置kafka(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
#服務端口默認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
#kafka數據的存儲目錄,一般都改爲逗號隔開的多個目錄(方便磁盤擴充)
log.dirs=/tmp/kafka/db0
# 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
# 日誌保留策略1-副本保留多長時間
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.
# 日誌保留策略2-副本超過多少字節
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
四、啓動kafka:
[root@javaxiaobang kafka]# bin/kafka-server-start.sh config/server-0.properties > kafka-0.log &
[2] 7761
[root@javaxiaobang kafka]# bin/kafka-server-start.sh config/server-1.properties > kafka-1.log &
[3] 8126
[root@javaxiaobang kafka]# bin/kafka-server-start.sh config/server-2.properties > kafka-2.log &
[4] 8493
[root@javaxiaobang kafka]#
五、創建主題：
[root@javaxiaobang kafka]# bin/kafka-topics.sh --create --bootstrap-server 123.56.224.5:9092 --replication-factor 3 --partitions 3 --topic test-topic
[root@javaxiaobang kafka]# bin/kafka-topics.sh --describe --bootstrap-server 123.56.224.5:9092 --topic test-topic
Topic:test-topic PartitionCount:3 ReplicationFactor:3 Configs:segment.bytes=1073741824
Topic: test-topic Partition: 0 Leader: 2 Replicas: 2,1,0 Isr: 2,1,0
Topic: test-topic Partition: 1 Leader: 1 Replicas: 1,0,2 Isr: 1,0,2
Topic: test-topic Partition: 2 Leader: 0 Replicas: 0,2,1 Isr: 0,2,1
六、發送消息：
[root@javaxiaobang kafka]# bin/kafka-console-producer.sh --broker-list 123.56.224.5:9092 --topic test-topic
>第一條消息
>第二條消息
>第三條消息
>
七、消費消息：
[root@javaxiaobang kafka]# bin/kafka-console-consumer.sh --bootstrap-server 123.56.224.5:9092 --from-beginning --topic test-topic
第一條消息
第二條消息
第三條消息
八、刪除topic
[root@javaxiaobang kafka]# bin/kafka-topics.sh --delete --bootstrap-server 123.56.224.5:9093 --topic javaxiaobangtopic
[root@javaxiaobang kafka]#
九、停止broker：
[root@javaxiaobang kafka]# bin/kafka-server-stop.sh
十、監控管理
https://github.com/quantifind/KafkaOffsetMonitor
java -cp KafkaOffsetMonitor-assembly-0.2.0.jar com.quantifind.kafka.offsetapp.OffsetGetterWeb --zk 127.0.0.1:2181 --port 9090 --refresh 10.seconds --retain 2.days &
十一、zookeeper監控工具：
java -jar zookeeper-dev-ZooInspector.jar
