three supported reliability levels: * End-to-end * Store on failure * Best effort
https://github.com/cloudera/flume/blob/master/flume-docs/src/docs/UserGuide/Introduction
=== Reliability | |
Reliability, the ability to continue delivering events in the face of | |
failures without losing data, is a vital feature of Flume. Large | |
distributed systems can and do suffer partial failures in many ways - | |
physical hardware can fail, resources such as network bandwidth or | |
memory can become scarce, or software can crash or run slowly. Flume | |
emphasizes fault-tolerance as a core design principle and keeps | |
running and collecting data even when many components have failed. | |
Flume can guarantee that all data received by an agent node will | |
eventually make it to the collector at the end of its flow as long as | |
the agent node keeps running. That is, data can be *reliably* | |
delivered to its eventual destination. | |
However, reliable delivery can be very resource intensive and is often | |
a stronger guarantee than some data sources require. Therefore, Flume | |
allows the user to specify, on a per-flow basis, the level of | |
reliability required. There are three supported reliability levels: | |
* End-to-end | |
* Store on failure | |
* Best effort | |
.A Note About Reliability | |
****************** | |
Although Flume is extremely tolerant to machine, network, and software | |
failures, there is never any such thing as '100% reliability'. If all | |
the machines in a Flume installation were irrevocably destroyed in | |
some terrible data center incident, all copies of Flume's data would | |
be lost and there would be no way to recover them. Therefore all of | |
Flume's reliability levels make guarantees about data delivery 'until | |
some maximum number of failures have occurred'. Flume's failure modes | |
- in terms of what can fail and what will keep running if they do - | |
are described in detail later in this guide. | |
****************** | |
The *end-to-end* reliability level guarantees that once Flume accepts | |
an event, that event will make it to the endpoint - as long as the | |
agent that accepted the event remains live long enough. The first | |
thing the agent does in this setting is write the event to disk in a | |
''write-ahead log'' (WAL) so that, if the agent crashes and restarts, | |
knowledge of the event is not lost. After the event has successfully | |
made its way to the end of its flow, an acknowledgment is sent back to | |
the originating agent so that it knows it no longer needs to store the | |
event on disk. This reliability level can withstand any number of | |
failures downstream of the initial agent. | |
The *store on failure* reliability level causes nodes to only require | |
an acknowledgement from the node one hop downstream. If the sending | |
node detects a failure, it will store data on its local disk until the | |
downstream node is repaired, or an alternate downstream destination | |
can be selected. While this is effective, data can be lost if a | |
compound or silent failure occurs. | |
The *best-effort* reliability level sends data to the next hop with no | |
attempts to confirm or retry delivery. If nodes fail, any data that | |
they were in the process of transmitting or receiving can be | |
lost. This is the weakest reliability level, but also the most | |
lightweight. |
=== Reliability | |
Reliability, the ability to continue delivering events in the face of | |
failures without losing data, is a vital feature of Flume. Large | |
distributed systems can and do suffer partial failures in many ways - | |
physical hardware can fail, resources such as network bandwidth or | |
memory can become scarce, or software can crash or run slowly. Flume | |
emphasizes fault-tolerance as a core design principle and keeps | |
running and collecting data even when many components have failed. | |
Flume can guarantee that all data received by an agent node will | |
eventually make it to the collector at the end of its flow as long as | |
the agent node keeps running. That is, data can be *reliably* | |
delivered to its eventual destination. | |
However, reliable delivery can be very resource intensive and is often | |
a stronger guarantee than some data sources require. Therefore, Flume | |
allows the user to specify, on a per-flow basis, the level of | |
reliability required. There are three supported reliability levels: | |
* End-to-end | |
* Store on failure | |
* Best effort | |
.A Note About Reliability | |
****************** | |
Although Flume is extremely tolerant to machine, network, and software | |
failures, there is never any such thing as '100% reliability'. If all | |
the machines in a Flume installation were irrevocably destroyed in | |
some terrible data center incident, all copies of Flume's data would | |
be lost and there would be no way to recover them. Therefore all of | |
Flume's reliability levels make guarantees about data delivery 'until | |
some maximum number of failures have occurred'. Flume's failure modes | |
- in terms of what can fail and what will keep running if they do - | |
are described in detail later in this guide. | |
****************** | |
The *end-to-end* reliability level guarantees that once Flume accepts | |
an event, that event will make it to the endpoint - as long as the | |
agent that accepted the event remains live long enough. The first | |
thing the agent does in this setting is write the event to disk in a | |
''write-ahead log'' (WAL) so that, if the agent crashes and restarts, | |
knowledge of the event is not lost. After the event has successfully | |
made its way to the end of its flow, an acknowledgment is sent back to | |
the originating agent so that it knows it no longer needs to store the | |
event on disk. This reliability level can withstand any number of | |
failures downstream of the initial agent. | |
The *store on failure* reliability level causes nodes to only require | |
an acknowledgement from the node one hop downstream. If the sending | |
node detects a failure, it will store data on its local disk until the | |
downstream node is repaired, or an alternate downstream destination | |
can be selected. While this is effective, data can be lost if a | |
compound or silent failure occurs. | |
The *best-effort* reliability level sends data to the next hop with no | |
attempts to confirm or retry delivery. If nodes fail, any data that | |
they were in the process of transmitting or receiving can be | |
lost. This is the weakest reliability level, but also the most | |
lightweight. |
three supported reliability levels: * End-to-end * Store on failure * Best effort的更多相关文章
- SignalR Supported Platforms -摘自网络
SignalR is supported under a variety of server and client configurations. In addition, each transpor ...
- store操作
store.remove(rs); store.sync({ success: function (e, opt) { this.store.commitChanges(); }, failure: ...
- extjs 解决使用store.sync()方法更新item有时不触发后台action的问题
问题描述: extjs 解决使用store.sync()方法更新item有时不触发后台action,不出发后台action的原因是item的字段值没有变化 解决方法: item.setDirty(tr ...
- PMP用语集
AC actual cost 实际成本 ACWP actual cost of work performed 已完工作实际成本 BAC budget at completion 完工预算 BCWP b ...
- Solaris10安装配置LDAP(iPlanet Directory Server )
Solaris10安装光盘自带了iPlanet Directory Server安装包,系统管理员可以利用iPlanet Directory Server在Solaris系统创建一个LDAP Serv ...
- memory ordering 内存排序
Memory ordering - Wikipedia https://en.wikipedia.org/wiki/Memory_ordering https://zh.wikipedia.org/w ...
- Web测试介绍2一 安全测试
安全测试是在IT软件产品的生命周期中,特别是产品开发基本完成到发布阶段,对产品进行检验以验证产品符合安全需求定义和产品质量标准的过程. 主要安全需求包括: (i) 认证 Authent ...
- Python 3.6.0的sqlite3模块无法执行VACUUM语句
Python 3.6.0的sqlite3模块存在一个bug(见issue 29003),无法执行VACUUM语句. 一执行就出现异常: Traceback (most recent call last ...
- Flume1.5.0的安装、部署、简单应用(含伪分布式、与hadoop2.2.0、hbase0.96的案例)
目录: 一.什么是Flume? 1)flume的特点 2)flume的可靠性 3)flume的可恢复性 4)flume 的 一些核心概念 二.flume的官方网站在哪里? 三.在哪里下载? 四.如何安 ...
随机推荐
- input弹出的手机键盘搜索事件
一.input的搜索框 在input标签里面把type设置为search就可以了.弹出的手机键盘回车键也会变成搜索或者是搜索的图标. <input id="search" ...
- 快充 IC BQ25896 的 常用參數
一: POWER-PATH MANAGEMENT (有接 adapter) 1:Vbat > Vsysmin,Isys = 0A, BATFET disable Vsys = Vbat + 50 ...
- poj 3308(二分图的点权最小覆盖)
Paratroopers Time Limit: 1000MS Memory Limit: 65536K Total Submissions: 8325 Accepted: 2502 Desc ...
- 不要使用 reader.Peek() 去读取每行数据
1.问题描述 使用SteamRead的Peek()和ReadLine()来读取流中的数据,如果数据行数太多,会读取不完整(后面有些数据就读不出来了). 比如: while (srResponseRea ...
- django中表变更后migrate无效的问题
问题描述: 已有的model,修改之后,想重新建模,于是将migrations文件夹中除__init__.py之外其他文件都删掉,再次执行以下步骤python manage.py makemigrat ...
- 【UTR #2】题目交流通道
题目描述 定好了难度,雄心勃勃的吉米多出题斯基开始寻找智慧的神犇星球的居民出题. 然而吉米多出题斯基没有料到,神犇星球的居民告诉吉米多出题斯基:"今年神犇星球经济不景气,大家都想宅在家里,哪 ...
- Codeforces 235 C
题目大意 给定一个模板串, 再给出\(n\)个询问, 询问每一个串的循环串总共在原串中出现了多少次. 循环串: 比如说有\(str[] = \{ABCD\}\), 则其循环串有\(\{ABCD\}, ...
- pv,uv
1.PV PV(page view),即页面浏览量:用户每1次对网站中的每个网页访问均被记录1次.用户对同一页面的多次访问,访问量累计. 2.什么是UV uv(unique visitor),指访问某 ...
- 如果当前地图文档中有独立的Table,通过Engine如何获取该Table?
将IMap转为ITableCollection,通过ITableCollection.get_Table(int index);来获取该Table
- go 依赖包管理工具gb安装报错
尝试了下gb工具,发现有个问题: [root@etcd1 test]# go get github.com/constabulary/gb/... /home/gopath/src/github.co ...