笔记本电脑电池不耐用_数据存储系统的可靠性，耐用性和可用性之间有何区别？...

笔记本电脑电池不耐用

Some important concepts in distributed system like Hadoop distributed file system, Google file system and so on.

分布式系统中的一些重要概念，例如Hadoop分布式文件系统，Google文件系统等。

Answer from http://www.quora.com/Whats-the-difference-between-Reliability-Durability-and-Availability-for-data-storage-system

来自http://www.quora.com/Whats-the-difference-between-Reliability-Durability-and-Availability-for-data-storage-system的答案

The difference between durability and availability is fairly simple. Durability is about what happens when all power goes out everywhere. Has all data been written to stable storage that doesn’t require power (e.g. disk/flash), in a form that allows it to be brought back and used? Availability is about what happens when there’s a partial failure – a disk, a node, a network. Does the system continue to operate and provide the same services it originally did?

耐用性和可用性之间的区别非常简单。 持久性是指所有电源无处不在时发生的情况。 是否已将所有数据以允许带回并使用的形式写入不需要电源的稳定存储（例如磁盘/闪存）中？ 可用性是关于部分故障（磁盘，节点， 网络）发生的情况 。 系统是否继续运行并提供与原来相同的服务？

Availability comes in multiple forms. To people who have worked on old-school HA – heartbeat, pairwise failover, address takeover, STONITH – it means system availability – the system as a whole continues to provide the original service. In a more recent CAP Theorem context it means node availability – the individual nodes (except those that have failed) continue to provide the original service. This precludes shutting down non-quorum nodes to preserve consistency, which is a common solution in the older HA world. This difference causes a lot of confusion, just like the C in CAP vs. the C in ACID, but it’s pretty well entrenched so you just have to keep the audience in mind when talking about availability.

可用性有多种形式。 人谁对老派的HA工作-心跳，成对的故障转移，地址接管，STONITH -这意味着系统可用性-该系统作为一个整体继续提供原有的服务。 在较新的CAP定理上下文中，这意味着节点可用性–单个节点（发生故障的节点除外）继续提供原始服务。 这避免了关闭非仲裁节点以保持一致性，这是较早的HA世界中的常见解决方案。 这种差异会引起很多混乱，就像CAP中的C与ACID中的C一样，但它根深蒂固，因此您在谈论可用性时只需记住受众。

Some people use “reliable” as a synonym for “available”. Some use it to distinguish system availability from node availability[1]. Some use it to mean ability to reach consensus despite faults[2] (basically C in CAP). Most people are just plain sloppy and don’t have any particular definition in mind (much like “fast” or “scalable”). Because there’s no consensus (heh) on its meaning, I’d suggest avoiding the term.

有些人将“可靠”用作“可用”的同义词。 一些人用它来区分系统可用性和节点可用性[1]。 一些人用它来表示尽管有错误[2]（CAP中基本为C）但仍能达成共识的能力。 大多数人只是草率的，没有特别的定义（很像“快速”或“可扩展”）。 由于对其含义尚无共识（heh），因此建议您避免使用该术语。

[1] 14 An Introduction to Distributed Systems http://webdam.inria.fr/Jorge/html/wdmch15.html
[2] Reliability of Distributed Systems http://www.cse.scu.edu/~jholliday/REL-EAR.htm

[1] 14分布式系统简介http://webdam.inria.fr/Jorge/html/wdmch15.html
[2]分布式系统的可靠性http://www.cse.scu.edu/~jholliday/REL-EAR.htm

Answered by harryxiyou.

由harryxiyou回答。

翻译自: https://www.systutorials.com/whats-the-difference-between-reliability-durability-and-availability-for-data-storage-system/

笔记本电脑电池不耐用