centos7+kafka集群搭建

1.官网下载kafka_2.11-0.10.1.0.tgz

2.在/home/develop(当前登录用户)新建kafka目录，mkdir kafka

3.进入kafka目录，cd /home/develop/kafka

4.执行tar -xzvf /home/develop/packages/kafka_2.11-0.10.1.0.tgz -C .

5.mkdir kafkaLogs,新建kafkaLog目录

6.修改kafka的配置文件，目录在 /home/develop/kafka/kafka_2.11-0.10.1.0/config/server.properties

7.修改server.properties的配置如下

# The id of the broker. This must be set to a unique integer for each broker.
broker.id=1

# Switch to enable topic deletion or not, default value is false
#delete.topic.enable=true

############################# 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 = security_protocol://host_name:port
#   EXAMPLE:
#     listeners = PLAINTEXT://your.host.name:9092
listeners=PLAINTEXT://10.212.130.12: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

# 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=/home/develop/kafka/kafkaLogs

# 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
message.max.bytes=5048576
default.replication.factor=2
replica.fetch.max.bytes=5048576

# 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.connect=10.212.130.6:2181,10.212.130.12:2181,10.212.130.13:2181

# Timeout in ms for connecting to zookeeper

zookeeper.connection.timeout.ms=6000

7.在其他kafka集群的机子上也进行同步操作

8.centos 7 开发kafka提供服务端口9092

9.firewall-cmd --zone=public --add-port=9092/tcp --permanent

10.启动kafka

11.先进入kafka的bin目录 cd /home/develop/kafka/kafka_2.11-0.10.1.0/bin

12.执行./kafka-server-start.sh ../config/server.properties & ；启动kafka服务

13.集群中其他节点的kafka服务也如此启动

14.执行jps

15.结果如下

[develop@cast1 bin]$ jps
25617 Kafka
18413 Jps

12846 QuorumPeerMain

16.有运行的kafka服务，则说明kafka集群运行正常，接下运行简单的生产者消费者测试kafka

17.测试命令如下

关于kafka新建一个topic的命令

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

查看当前集群上的所有的topic
2../kafka-topics.sh --zookeeper 10.212.130.10:2181 --list

创建一个生产者
3./kafka-console-producer.sh --broker-list 10.212.130.10:9092 --topic test

创建一个消费者的   
4../kafka-console-consumer.sh  --bootstrap-server 10.212.130.10:9092 --topic test --from-beginning