今天需要在新机器上安装一个kafka集群，其实kafka我已经装了十个不止了，但是没有一个是为生产考虑的，因此比较汗颜，今天好好地把kafka的安装以及配置梳理一下；
1，kafka版本选取；
现在我写博客的时候kafka的最新版本是1.1.0，如果最新版本稳定我就直接用最新的了，但是不一定稳定，因此，我先观望一下，kafka地址：http://kafka.apache.org/downloads；
2，zookeeper版本选取；
去zookeeper的官网分析了一下zookeeper的版本，也没选出来个所以然，刚想下载3.4.10版本，去了下载页面没想到有一个目录就放着稳定版本：http://mirror.bit.edu.cn/apache/zookeeper/stable/，因此直接就选他啦，3.4.12版本；
3，服务器环境调试；
发现没有装jdk，装上；、
防火墙先关闭；
selinux关闭；
4，zookeeper安装；
我把zookeeper的压缩文件放到了root目录下了，先到/opt目录下，然后：
执行：tar -zxvf /root/zookeeper-3.4.12.tar.gz 将文件解压；
执行： mv zookeeper-3.4.12 zookeeper 将文件重命名，主要是为了方便；
执行： cd /opt/zookeeper/conf 进入zookeeper的配置目录；
执行：mv zoo_sample.cfg zoo.cfg 将示例配置文件重命名；
执行：vi zoo.cfg 开始配置zookeeper，其实没什么需要改的，人家本来的配置就够用的了，如果说有需要的话，那就把允许的最大连接数改大，我改成了300，直接上配置文件，我这里是配置了三台zookeeper，如果多的话自己加上自己的机器就好，把文件中的地址改掉就好了：
# The number of milliseconds of each tick
tickTime=
# The number of ticks that the initial
# synchronization phase can take
initLimit=
# The number of ticks that can pass between
# sending a request and getting an acknowledgement
syncLimit=
# the directory where the snapshot is stored.
# do not use /tmp for storage, /tmp here is just
# example sakes.
dataDir=/data1/zookeeper
# the port at which the clients will connect
clientPort=
# the maximum number of client connections.
# increase this if you need to handle more clients
maxClientCnxns=
#
# Be sure to read the maintenance section of the
# administrator guide before turning on autopurge.
#
# http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance
#
# The number of snapshots to retain in dataDir
#autopurge.snapRetainCount=
# Purge task interval in hours
# Set to "" to disable auto purge feature
#autopurge.purgeInterval=
server.=10.16.26.110:: server.=10.16.26.116:: server.=10.16.26.127::
执行：mkdir /data1/zookeeper 先把zookeeper的文件目录创建出来；
执行：cd /data1/zookeeper 进入此目录；
执行：vi myid 创建一个叫myid的文件，此文件中用来表示本台机器的id是多少，放在咱们的集群里肯定就是1/2/3啦；
这样zookeeper就配置完了，按照此步骤把几台机器都配置好；
4，kafka参数配置；
新版本的kafka已经很好用了，不需要做 太多的配置；
# 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= ############################# 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://10.16.26.110: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= # The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads= # The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes= # The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes= # The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes= ############################# Log Basics ############################# # A comma separated list of directories under which to store log files
log.dirs=/data1/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= delete.topic.enable=true default.replication.factor= # 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= ############################# 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 is recommended for to ensure availability such as .
offsets.topic.replication.factor=
transaction.state.log.replication.factor=
transaction.state.log.min.isr= ############################# 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:
# . Durability: Unflushed data may be lost if you are not using replication.
# . 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.
# . 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= # The maximum amount of time a message can sit in a log before we force a flush
#log.flush.interval.ms= ############################# 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= # 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= # The maximum size of a log segment file. When this size is reached a new log segment will be created.
log.segment.bytes= # 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= ############################# 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.16.26.110:,10.16.26.126:,10.16.26.127: # Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms= ############################# 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 seconds.
# We override this to here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup.
group.initial.rebalance.delay.ms=
kafka 配置
5，kafka安装；
和zookeeper查不多，解压然后根据上一步的配置配置好就可以了；
6，zookeeper以及kafka启动；
zookeeper启动，进入zookeeper的bin目录下然后执行：./zkServer.sh start ;即可，然后其他两台也如此执行；
kakfa启动：进入kafka的bin目录执行：./kafka-server-start.sh -daemon ../config/server.properties &