linux系统kafka集群搭建（3个节点192.168.204.128、192.168.204.129、192.168.204.130）
本篇文章kafka集群采用外部zookeeper,没采用自带zookeeper
1、创建文件夹/usr/local/kafka,下载kafka2.11-2.0.0至/usr/local/kafka,解压重命名为kafka；
2、进入kafka文件中的config，即/usr/local/kafka/kafka/config, 编辑文件server.properties
#############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, .......
#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,......
# The number of threads that the server uses for receiving ......
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=/var/log/kafka
# 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 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......
# 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集群3个节点分别为192.168.204.128、192.168.204.129、192.168.204.130）
zookeeper.connect=192.168.204.128:2181,192.168.204.129:2181,192.168.204.130:2181
# Timeout in ms for connecting to zookeeper
# 与zookeeper连接超时时间
zookeeper.connection.timeout.ms=6000
# 该值最好设置大于15000，否则kafka某个节点可能会连不上zookeeper，sessionTimeout
zookeeper.session.timeout.ms=25000
############ 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 ...
# 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
3、开启防火墙
在防火墙中增加端口项vi /etc/sysconfig/iptables
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9092 -j ACCEPT
然后重启防火墙 service iptables restart
4、配置环境变量
在 /etc/profile 中添加如下配置：
vi etc/profile 在最后添加如下两个。
export KAFKA_HOME=/usr/local/kafka/kafka
export PATH=$PATH:$KAFKA_HOME/bin
保存后进入cd /etc目录下，输入source profile命令使修改生效。
5、在其它两个节点作上述同样操作，记得server.properties文件中的broker.id要不一样，
同时在/var/log/中创建文件夹kafka。
6、进入每个节点的/usr/local/kafka/kafka/bin/
输入./kafka-server-start.sh ../config/server.properties &
即启动kafka节点，出现如下，则成功启动
........
[2018-10-11 20:22:17,663] INFO [TransactionCoordinator id=0] Starting up.
(kafka.coordinator.transaction.TransactionCoordinator)
[2018-10-11 20:22:17,681] INFO [TransactionCoordinator id=0] Startup complete.
(kafka.coordinator.transaction.TransactionCoordinator)
[2018-10-11 20:22:17,708] INFO [Transaction Marker Channel Manager 0]: Starting
(kafka.coordinator.transaction.TransactionMarkerChannelManager)
[2018-10-11 20:22:18,159] INFO [/config/changes-event-process-thread]: Starting
(kafka.common.ZkNodeChangeNotificationListener$ChangeEventProcessThread)
[2018-10-11 20:22:18,185] INFO [SocketServer brokerId=0] Started processors for 1 acceptors
(kafka.network.SocketServer)
[2018-10-11 20:22:18,203] INFO Kafka version : 2.0.0 (org.apache.kafka.common.utils.AppInfoParser)
[2018-10-11 20:22:18,204] INFO Kafka commitId : 3402a8361b734732
(org.apache.kafka.common.utils.AppInfoParser)
[2018-10-11 20:22:18,219] INFO [KafkaServer id=0] started (kafka.server.KafkaServer)