Kafka 学习笔记

Kafka 学习笔记

原创编写： 王宇 
2016-10-24

---

 

Kafka 笔记
消息系统(Messaging System)
Kafka 结构
集群结构（Cluster Architecture）
WorkFlow
安装步骤
Kafka 基本操作
Simple Producer Example
Simple Consumer Example
参考

 

---

消息系统(Messaging System)

• Point to Point Messaging System 
  
  
   
• Publish-Subscribe Messaging System 
  
  
   

两者最主要的区别是 Publish-Subscribe 模式支持多 Receiver

Kafka 结构

 

Components	Description
Topics	A stream of messages belonging to a particular category is called a topic. Data is stored in topics.Topics are split into partitions. For each topic, Kafka keeps a mini-mum of one partition. Each such partition contains messages in an immutable ordered sequence. A partition is implemented as a set of segment files of equal sizes.
Partition	Topics may have many partitions, so it can handle an arbitrary amount of data.
Partition offset	Each partitioned message has a unique sequence id called as offset.
Replicas of partition	Replicas are nothing but backups of a partition. Replicas are never read or write data. They are used to prevent data loss.
Brokers	Brokers are simple system responsible for maintaining the pub-lished data. Each broker may have zero or more partitions per topic. Assume, if there are N partitions in a topic and N number of brokers, each broker will have one partition.Assume if there are N partitions in a topic and more than N brokers (n + m), the first N broker will have one partition and the next M broker will not have any partition for that particular topic.Assume if there are N partitions in a topic and less than N brokers (n-m), each broker will have one or more partition sharing among them. This scenario is not recommended due to unequal load distri-bution among the broker.
Kafka cluster	Kafka’s having more than one broker are called as Kafka cluster. A Kafka cluster can be expanded without downtime. These clusters are used to manage the persistence and replication of message data.
Producers	Producers are the publisher of messages to one or more Kafka topics. Producers send data to Kafka brokers. Every time a producer pub-lishes a message to a broker, the broker simply appends the message to the last segment file. Actually, the message will be appended to a partition. Producer can also send messages to a partition of their choice.
Consumers	Consumers read data from brokers. Consumers subscribes to one or more topics and consume published messages by pulling data from the brokers.
Leader	Leader is the node responsible for all reads and writes for the given partition. Every partition has one server acting as a leader.
Follower	Node which follows leader instructions are called as follower. If the leader fails, one of the follower will automatically become the new leader.A follower acts as normal consumer, pulls messages and up-dates its own data store.

集群结构（Cluster Architecture）

 

Components	Description
Broker	Kafka cluster typically consists of multiple brokers to maintain load balance. Kafka brokers are stateless, so they use ZooKeeper for maintaining their cluster state. One Kafka broker instance can handle hundreds of thousands of reads and writes per second and each bro-ker can handle TB of messages without performance impact. Kafka broker leader election can be done by ZooKeeper.
ZooKeeper	ZooKeeper is used for managing and coordinating Kafka broker. ZooKeeper service is mainly used to notify producer and consumer about the presence of any new broker in the Kafka system or failure of the broker in the Kafka system. As per the notification received by the Zookeeper regarding presence or failure of the broker then pro-ducer and consumer takes decision and starts coordinating their task with some other broker.
Producers	Producers push data to brokers. When the new broker is started, all the producers search it and automatically sends a message to that new broker. Kafka producer doesn’t wait for acknowledgements from the broker and sends messages as fast as the broker can handle.
Consumers	Since Kafka brokers are stateless, which means that the consumer has to maintain how many messages have been consumed by using partition offset. If the consumer acknowledges a particular message offset, it implies that the consumer has consumed all prior messages. The consumer issues an asynchronous pull request to the broker to have a buffer of bytes ready to consume. The consumers can rewind or skip to any point in a partition simply by supplying an offset value. Consumer offset value is notified by ZooKeeper.

WorkFlow

Kafka 是一个通过topics分割到一个或多个partitions的collection. 一个Kafka partition 是一个线性有序的messages, 每一个message通过索引标识

• Workflow of Pub-Sub Messaging

  • Producers send message to a topic at regular intervals.
  • Kafka broker stores all messages in the partitions configured for that particular topic. It ensures the messages are equally shared between partitions. If the producer sends two messages and there are two partitions, Kafka will store one message in the first partition and the second message in the second partition.
  • Consumer subscribes to a specific topic.
  • Once the consumer subscribes to a topic, Kafka will provide the current offset of the topic to the consumer and also saves the offset in the Zookeeper ensemble.
  • Consumer will request the Kafka in a regular interval (like 100 Ms) for new messages.
  • Once Kafka receives the messages from producers, it forwards these messages to the consumers.
  • Consumer will receive the message and process it.
  • Once the messages are processed, consumer will send an acknowledgement to the Kafka broker.
  • Once Kafka receives an acknowledgement , it changes the offset to the new value and updates it in the Zookeeper. Since offsets are maintained in the Zookeeper, the consumer can read next message correctly even during server outrages.
  • This above flow will repeat until the consumer stops the request.
  • Consumer has the option to rewind/skip to the desired offset of a topic at any time and read all the subsequent messages.

• Workflow of Queue Messaging / Consumer Group 
  一个consumers组有相同的Group ID 去 Subscribe 一个Topic.

  • Producers send message to a topic in a regular interval.
  • Kafka stores all messages in the partitions configured for that particular topic similar to the earlier scenario.
  • A single consumer subscribes to a specific topic, assume Topic-01 with Group ID as Group-1.
  • Kafka interacts with the consumer in the same way as Pub-Sub Messaging until new consumer subscribes the same topic, Topic-01 with the same Group ID as Group-1.
  • Once the new consumer arrives, Kafka switches its operation to share mode and shares the data between the two consumers. This sharing will go on until the number of con-sumers reach the number of partition configured for that particular topic.
  • Once the number of consumer exceeds the number of partitions, the new consumer will not receive any further message until any one of the existing consumer unsubscribes. This scenario arises because each consumer in Kafka will be assigned a minimum of one partition and once all the partitions are assigned to the existing consumers, the new consumers will have to wait.
  • This feature is also called as Consumer Group. In the same way, Kafka will provide the best of both the systems in a very simple and efficient manner.

• Role of ZooKeeper 
  A critical dependency of Apache Kafka is Apache Zookeeper, which is a distributed configuration and synchronization service. Zookeeper serves as the coordination interface between the Kafka brokers and consumers. The Kafka servers share information via a Zookeeper cluster. Kafka stores basic metadata in Zookeeper such as information about topics, brokers, consumer offsets (queue readers) and so on.

安装步骤

• 步骤一： 安装JDK 并配置环境变量 JAVA_HOME CLASSPATH

• 步骤二 : 安装ZooKeeper

  下载ZooKeeper 
  解包

  1. $ tar xzvf zookeeper-3.5.2-alpha.tar.gz
  2. $ mv ./zookeeper-3.5.2-alpha /opt/zookeepter
  3. $ cd /opt/zookeeper
  4. $ mkdir data

  创建配置文件

  1. $ cd /opt/zookeeper
  2. $ vim conf/zoo.cfg
  4. tickTime=2000
  5. dataDir=/opt/zookeeper/data
  6. clientPort=2181
  7. initLimit=5
  8. syncLimit=2

  启动ZooKeeper Seve

  1. $ bin/zkServer.sh start

• 步骤三安装 SLF4J

  下载 SL4J : slf4j-1.7.21.tar.gz www.slf4j.org 
  解包并配置CLASSPATH

  1. $ tar xvzf ./slf4j-17.21.tar.gz
  2. $ mv ./slf4j-17.21/op/slf4j
  3. vim ~/.bashrc
  4. export CLASSPATH = ${ CLASSPATH}:/opt/slf4j/*

• 步骤四： 安装 Kafka

  下载 Kafka 
  解包

  1. $ tar xzvf kafka_2.11-0.10.