【Kafka十二】关于Kafka是一个Commit Log Service-技术博客集

【Kafka十二】关于Kafka是一个Commit Log Service
编程技术 / houtizong 发布于 3年前 71

Kafka is a distributed, partitioned, replicated commit log service.这里的commit log如何理解？

A message is considered "committed" when all in sync replicas for that partition have applied it to their log. Only committed messages are ever given out to the consumer. This means that the consumer need not worry about potentially seeing a message that could be lost if the leader fails. Producers, on the other hand, have the option of either waiting for the message to be committed or not, depending on their preference for tradeoff between latency and durability. This preference is controlled by the request.required.acks setting that the producer uses.

The guarantee that Kafka offers is that a committed message will not be lost, as long as there is at least one in sync replica alive, at all times.

Kafka will remain available in the presence of node failures after a short fail-over period, but may not remain available in the presence of network partitions.

Kafka是一个基于副本的高可靠的消息系统，在消息可用前，Kafka保证消息已经提交到足够的副本中（这个在min.insync.replicas中配置），这种逻辑类似于Zookeeper的写操作(Leader写，然后指定个数的Follower完成同步）。

Kafka不同于Zookeeper，Zookeeper是可以在网络发生分区后，能够继续工作

上一篇：【Kafka十一】关于Kafka的副本管理

下一篇：【Hive十一】Hive数据倾斜优化

请勿发布不友善或者负能量的内容。与人为善，比聪明更重要！

<div > Kafka is a distributed, partitioned, replicated commit log service.这里的commit log如何理解？ &nbsp; A message is considered &quot;committed&quot; when all in sync replicas for that partition have applied it to their log. Only committed messages are ever given out to the consumer. This means that the consumer need not worry about potentially seeing a message that could be lost if the leader fails. Producers, on the other hand, have the option of either waiting for the message to be committed or not, depending on their preference for tradeoff between latency and durability. This preference is controlled by the request.required.acks setting that the producer uses. &nbsp; The guarantee that Kafka offers is that a committed message will not be lost, as long as there is at least one in sync replica alive, at all times. Kafka will remain available in the presence of node failures after a short fail-over period, but may not remain available in the presence of network partitions. &nbsp; Kafka是一个基于副本的高可靠的消息系统，在消息可用前，Kafka保证消息已经提交到足够的副本中（这个在min.insync.replicas中配置），这种逻辑类似于Zookeeper的写操作(Leader写，然后指定个数的Follower完成同步）。 &nbsp; Kafka不同于Zookeeper，Zookeeper是可以在网络发生分区后，能够继续工作 &nbsp; </div>

留言需要登陆哦

技术博客集 - 网站简介：
前后端技术：
后端基于Hyperf2.1框架开发,前端使用Bootstrap可视化布局系统生成
网站主要作用：
1.编程技术分享及讨论交流，内置聊天系统;
2.测试交流框架问题，比如：Hyperf、Laravel、TP、beego;
3.本站数据是基于大数据采集等爬虫技术为基础助力分享知识，如有侵权请发邮件到站长邮箱，站长会尽快处理;
4.站长邮箱：[email protected];

文章归档

文章标签

友情链接

首页
关于我们

Auther ·HouTiZong: 侯体宗的博客