分布式系统中容错技术摘要.pptVIP

Lecture 7- 第 7 章 分布式系统中容错技术 一台计算机由各种各样的硬件和软件组成，这些部件时不时地会出现故障或错误，导致死机或运行失败。 这些故障或错误往往是随机出现的，计算机用户无法预料这些情况的出现，有时甚至察觉不到错误的出现 。 如果一个计算机系统能够对非预期的软件/硬件故障有适当的对策和应变措施，则我们说这个系统具备一定的容错(Fault tolerance) 能力。 分布式系统的特殊之处在于故障的局部化，即系统的某个(些) 局部成份出现故障，这种故障可能会影响到系统的局部功能，而对系统的其它部分毫无影响。 本章讨论内容包括容错处理的基本概念、要求和模型，如何实现可靠的通信，以及当发现故障时如何排除并恢复运行 。 当系统不能提供所承诺的服务时就认为系统失效 一个系统在正常工作时会在若干种运行状态之间变迁，一旦出现异常，则该系统进入错误(Error) 状态。一个系统的错误状态可能是导致系统失效的原因 造成错误的原因称为故障。 Passive (Primary-Backup) Replication Request Communication: the request is issued to the primary RM and carries a unique request id. Coordination: Primary takes requests atomically, in order, checks id (resends response if not new id.) Execution: Primary executes stores the response Agreement: If update, primary sends updated state/result, req-id and response to all backup RMs. Response: primary sends to the front end Fault Tolerance in Passive Replication The system implements linearizability, since the primary sequences operations in order. If the primary fails, a backup becomes primary by leader election, and the replica managers that survive agree on which operations had been performed at the point when the new primary takes over. The above requirement is met if the replica managers (primary and backups) are organized as a group and if the primary uses view-synchronous group communication to send updates to backups. The system remains linearizable after the primary crashes Active Replication Request Communication: The request contains a unique identifier and is multicast to all by a reliable totally ordered multicast. Coordination: Group comm. ensures that requests are delivered to each RM in the same order (but may be at different times!). Execution: Each replica executes the request. (Correct replicas return same result since they are running the same program, i.e., they are replicated protocols or replicated state machines) Agreement: No agreement phase is needed, because of multicast delivery semantics of requests Resp