Kafka集群的Linux安装步骤

 

一、  环境准备

Kafka依赖ZooKeeper，首先需要确保ZooKeeper服务已经搭建完成。

 

操作系统:

CentOS-7-x86_64-1611

 

节点IP端口:

192.168.2.200:9092

192.168.2.201:9092

192.168.2.202:9092

 

二、  Kafka安装

 

1. 下载Kafka

Kafka官网地址：http://kafka.apache.org/

 

cd /usr/local wget https://www.apache.org/dyn/closer.cgi?path=/kafka/0.11.0.0/kafka_2.11-0.11.0.0.tgz

 

2.  解压

cd /usr/local tar -zxvf kafka_2.11-0.11.0.0.tgz ls

 

三、  Kafka集群配置

 

1.  修改server.properties配置文件

cd /usr/local/kafka_2.11-0.11.0.0/config/ vi server.properties

server.properties修改后文件内容

############################# Server Basics #############################   # The id of the broker. This must be set to a unique integer for each broker. broker.id=0   # 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 = listener_name://host_name:port #   EXAMPLE: #     listeners = PLAINTEXT://your.host.name:9092 listeners=PLAINTEXT://192.168.2.200: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=1048576   # The receive buffer (SO_RCVBUF) used by the socket server socket.receive.buffer.bytes=1048576   # 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.11.0.0/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=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 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=20000   # The maximum amount of time a message can sit in a log before we force a flush log.flush.interval.ms=10000   ############################# 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=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. 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.connect=192.168.2.200:2181,192.168.2.201:2181,192.168.2.202:2181,192.168.2.203:2181,192.168.2.204: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

      在集群中每个节点的broker.id不同，类似zookeeper的myid

 

2.  启动kafka集群

cd /usr/local/kafka_2.11-0.11.0.0/ nohup bin/kafka-server-start.sh config/server.properties &

 

3.  创建主题

bin/kafka-topics.sh --create --zookeeper 192.168.2.200:2181,192.168.2.201:2181,192.168.2.202:2181,192.168.2.203:2181,192.168.2.204:2181 --replication-factor 3 --partitions 1 --topic CZ-ICBC-TOPIC

 

4. 查看主题状态

bin/kafka-topics.sh --describe --zookeeper 192.168.2.200:2181,192.168.2.201:2181,192.168.2.202:2181,192.168.2.203:2181,192.168.2.204:2181 --topic CZ-ICBC-TOPIC

 

 

5. 生产者生产数据

bin/kafka-console-producer.sh --broker-list 192.168.2.200:9092,192.168.2.201:9092,192.168.2.202:9092 --topic CZ-ICBC-TOPIC this is a message

 

6. 消费者消费数据

bin/kafka-console-consumer.sh --bootstrap-server 192.168.2.200:9092,192.168.2.201:9092,192.168.2.202:9092 --from-beginning --topic CZ-ICBC-TOPIC