Kafka知识点入门学习一

一：Kafka简介

1.  Kafka是什么
           
2. 消息队列内部实现原理
     
    

3. 为什么需要消息队列？
    
    
    

二：Kafka架构原理

1. kafka的特性
    ⑴高吞吐量、低延迟
            kafka每秒可以处理几十万条消息，它的延迟最低只有几毫秒，每个topic可以分多个partition, consumer group 对partition进行
            consume操作。
    ⑵可扩展性
            kafka集群支持热扩展
    ⑶持久性、可靠性
             消息被持久化到本地磁盘，并且支持数据备份防止数据丢失
    ⑷容错性
             允许集群中节点失败（若副本数量为n,则允许n-1个节点失败）
    ⑸高并发
              支持数千个客户端同时读写
2. Kafka的使用场景 
          

三：Kafka集群部署

1. 环境准备
    
    
    zookeeper集群，以及jdks等安装，在前面已经安装过了。
2. Kafka版本
    
3.  上传kafka到/opt/software目录下，并且解压到/opt/module目录下
    
    
4. 修改/opt/module/kafka_2.11-0.11.0.2/config目录下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的全局唯一编号，不能重复
   broker.id=0
   
   # Switch to enable topic deletion or not, default value is false
   #是否允许删除topic
   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://: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
   #用来处理磁盘IO的线程数量
   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
   #kafka运行日志存放的路径
   log.dirs=/opt/module/kafka_2.11-0.11.0.2/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.
   #topic在当前broker上的分区个数
   num.partitions=3
   
   # 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.
   #用来恢复和清理data下数据的线程数量
   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=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
   #segment文件保留的最长时间，超时将被删除
   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集群地址
   zookeeper.connect=hadoop102:2181,hadoop103:2181,hadoop104:2181
   
   # Timeout in ms for connecting to zookeeper
   #超时时间设置长一点
   zookeeper.connection.timeout.ms=60000
   
   
   ############################# 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
   

    

5. 修改/opt/module/kafka_2.11-0.11.0.2/config/目录下producer.properties,数据将会在所有servers上均衡加载 
    
6. 修改/opt/module/kafka_2.11-0.11.0.2/config/目录下consumer.properties
    
7.   将kafka分发到其它两台机器上
    
    
8.   分别修改其它两台机器kafka的broker_id
     
    
    
    
9. 先启动zookeeper集群
     
     
     
10. 启动kafka集群，依次在hadoop102、hadoop103、hadoop104节点上启动kafka
     a：进入/opt/module/kafka_2.11-0.11.0.2/目录下执行下面的命令
          bin/kafka-server-start.sh config/server.properties &