Pos/355 Failures

Failures

Justin Lawrence Lopez

POS/355

Abstract

A distributed system segment of software in a computer that coordinate with each other by exchanging messages. The system is dependent on a network that holds the routing of messages and connects the computer. Generally, distributed system as interpreted is an allocation of independent systems that interact together with the help of a computer network. All these computers across the distributed system operate under a common goal and strive to achieve a common task across these distributed systems.

Failures

This paper will describe the four types of failures that may occur in a distributive system and specify which of these are also applicable to a centralized system. Also, to choose two of the four failures and describe how you would isolate and fix each failure.

The four different types of failure that may occur across the distributed system are the following;

Crash Failure

Crash failures are generated from one side of the server to the other side of a typical distributed system and operations of the server come to stop for a while if crash failures take place. The best example for crash failure is the Operating System failures (Hardware and Software failure) and with respect to these an equivalent fault-tolerant system are expanded. Regularly to manage crashes require two steps. First, explicitly detect any failure whether if it is a software or hardware issues and then recover by starting again or failing over crashed pieces.

Crash failure is also called a halting failure, and this type of failure is also applicable to a centralized system such as a database. According to Jayaram and Varghese (1997), “Crash failures are common cause of protocol failures. Thus protocol designers work hard to ensure that their protocols are crash resilient. It is easy to make protocols crash resilient if each node has non-volatile memory (e.g., disk) that survive crashes. Non-volatile memory can even be used, on...