Resilient to single and multi-storage node failure
对单点或多点故障有很好的容错性
The chance of rack failure is far less than that of node failure;
机架失效的概率要远低于节点失效；
PowerHA detects three kinds of failures directly. Those are the network, NIC and node failure.
PowerHA直接探测三类故障：网络、NIC和节点故障。
A new algorithm for computing reliability of network with node failure is presented in this paper.
提出了一种用于计算具有节点失效的网络可靠度的新计算方法。
The basic operations of the protocol include: node joining, node exit, node failure restore, and node capability aggregation.
协议基本操作包括：节点加入、节点退出、节点失效恢复、节点能力度汇聚和节点关系更新。
RSCT detects the loss of heartbeat packets that are sent across all the networks and determines the exact loss (network, NIC or node failure).
RSCT实际上探测跨所有网络发送的心跳数据包是否丢失并判断准确的丢失(网络、NIC或节点故障)。
Balanced Application layer multicast Protocol overcomes the unbalance in node degree, distribution of flows, network delay, effect of node failure etc.
基于均衡的应用层组播协议克服了现有的应用层组播协议在节点负载、网络时延、流量分布、受失效节点影响等方面的不均衡。
On another hand, fault-tolerant mechanism depends on the quick detection of node failure, node failure detection is always performed by heartbeat protocol.
另一方面，集群操作系统的容错机制依赖于节点失效的快速检测，节点失效检测通常由心跳协议来完成。
In this mode, the Shared volume groups are accessible by multiple PowerHA nodes, which results in faster failover (disk takeover) in the event of a node failure.
在这种模式下，多个Power ha节点都可以访问共享卷组，这会加快发生节点故障时的故障转移(磁盘接管)。
Non-IP networks: An example is RS232 (this is needed to make sure that even if the network goes down, PowerHA is capable of differentiating between network failure and node failure)
非IP网络：例如RS232（为了确保即使在发生网络故障的情况下 PowerHA也能够区分网络故障和节点故障，需要非 IP 网络）
Distributed ESB has the merits of load balancing, allowing single node failure, and supporting persistent messaging. A distributed ESB also avoids producing the performance bottleneck.
分布式esb实现了总线负载均衡，克服了集中式架构存在的单点故障和性能瓶颈问题，并且支持消息传输的持久性。
A new deflection routing scheme is proposed to overcome the drawback of the existing deflection routing scheme, such as inability to handle node failure and suffering from routing loop.
提出了一种新的偏转路由方案，以解决现有偏转路由方案不能处理节点故障以及存在路由环路的问题。
This paper proposed a new self-healing mechanism based on pre-designed survivable ATM (Code division multiple access) multicast tree, which considers any single link and node failure case.
本文提出了一种采用预设计的方法生成可恢复ATM多播树的自愈机制，该机制考虑了多播树的任何单链路和单节点失效两种情况。
If the system is also stripped of the right to arbitrarily abort transactions (system aborts typically occur for reasons such as node failure and deadlock), then problem (b) is also eliminated.
如果系统还有权任意中止交易(系统中止通常发生故障，如节点和死锁的原因)，则问题剥离(二)也是消除。
You should now have all the components necessary to handle a failure of the master node, if it should occur.
现在您就已经拥有了处理主节点故障(如果它会发生)所需要的所有组成部分。
This ensures that the state can be recovered from either the scheduling node or the execution node in event of failure.
这样就确保了当调度节点或者执行节点出现故障时那些状态可以恢复。
For the second failure, case 1: If a fails, it is placed on the spare node.
对于第二次故障，情形1：如果A出现故障，它将被转移到空闲节点上。
The server will detect the failure and automatically submit the incomplete work to another node.
服务器会检测到这个故障，并自动将未完成的工作转移到另外一个节点。
It's still possible to lose data (for example, if both nodes failed), but failure of the primary node will not cause data loss, because the data has been replicated.
这仍然可能丢失数据(例如，如果两个节点都发生故障)，但是主节点故障不会引起数据丢失，因为数据已经被复制了。
Upon failure of the primary node the redundant node takes over.
在主节点发生故障时，冗余节点可以接管。
High availability, the requirement to protect a production-grade application against a failure of any node, isn't a new concept by any standard; many software products address this challenge.
高可用性—避免一个生产级应用程序在任何节点上发生故障的要求—对于任何标准而言都不是什么新概念；许多软件产品都致力于解决这个问题。
Note that the three input node event types (entry, exit, and failure) introduced in V6.1.0.2 are also supported.
请注意，还支持V6.1.0.2中引入的三个输入节点事件类型(进入、退出和失败)。
Even if a single active, 100% operational node loses connection to its peer systems due to network failure or if both the inactive peers halt simultaneously, the resource will be voluntarily released.
即使只有一个节点是活动的，完全运行的节点也会由于网络故障丢失它与同级系统之间的连接，或者，如果两个非活动的同级系统同时暂停，资源将被自动释放。
In the case of a hardware failure, the node can be easily recovered back to the last configuration reflected in the cell configuration maintained by the Deployment Manager.
一旦出现硬件故障，节点可以轻松恢复到DeploymentManager维护的单元配置中反映的最后配置。
PowerHA SystemMirror can be configured to fail over automatically to a backup node when a failure is detected on the production node, minimizing the need for system operator intervention.
PowerHASystemMirror可以配置为，当在生产节点上检测到故障时自动转移到备份节点，以尽可能不需要系统操作员的干预。
The callback function first determines whether the call was a success or a failure by accessing the first node in the response: the PHP file returns this result as a node named success or error.
回调函数首先通过访问响应的第一个节点来确定调用是成功还是失败：PHP文件以一个名为success or error的节点返回结果。
Laurent talked about 2 typical cases of failure and how JPPF fails over to a different node in these scenarios.
Laurent谈到了两个典型的关于故障转移的例子，并解释JPPF如何在这种情况下切换到一个不同的节点。
When a failure occurs within a given node, a reconfiguration is carried out by the Partition Manager to handle the failure.
当在指定的节点上发生了故障，那么区块管理器(Partition Manager)就会执行重新配置，从而处理这个故障。
For the second failure, case 2: If eCMDB is on the spare node, then the subsequent failure of ITIC will not change the status quo; however, Maximo will bump eCMDB from the spare node.
对于第二次故障，情形2：如果eCMD b位于空闲节点上，那么ITIC随后出现故障时将不会更改现状，但是Maximo将从空闲节点上转储ecmdb。
It has a fully decentralized model; every node is identical and there is no single point of failure.
他具有完全分散模型；所有的节点都是同一的，没有单点故障。
应用推荐