Failure handling



Rating - 3/5
546 views

 

These Topics Are Also In Your Syllabus
1 System Analyst As Change Of Agent , Investigator and Monitoring Guy , Architect , Psychologist , Motivator , Intermediary link
2 System development life cycle (SDLC) link
You May Find Something Very Interesting Here. link
3 Various phases of development - Analysis, Design, Development, Implementation, Maintenance link
4 Types of documentation and their importance link
5 Enforcing documentation discipline in an organization link

  

These Topics Are Also In Your Syllabus
1 Building the Baseline Project Plan link
2 Reviewing the Baseline Project Plan link
You May Find Something Very Interesting Here. link
3 Pine Valley Furniture WebStore: Systems Planning and Selection link
4 Performing Requirements Determination link
5 Traditional Methods for Determining Requirements link

Computer systems sometimes fail. When faults occur in hardware or software, programs may produce incorrect results or may stop before they have completed the intended computation. We shall discuss and classify a range of possible failure types that can
occur in the processes and networks that comprise a distributed system. Failures in a distributed system are partial – that is, some components fail while others continue to function. Therefore the handling of failures is particularly difficult.
The following techniques for dealing with failures are discussed throughout the book:
Detecting failures: Some failures can be detected. For example, checksums can be used to detect corrupted data in a message or a file. Chapter 2 explains that it is difficult or even impossible to detect some other failures, such as a remote crashed server in the Internet. The challenge is to manage in the presence of failures that cannot be detected but may be suspected.
Masking failures: Some failures that have been detected can be hidden or made less severe. Two examples of hiding failures:
1. Messages can be retransmitted when they fail to arrive.
2. File data can be written to a pair of disks so that if one is corrupted, the other may still be correct.
Just dropping a message that is corrupted is an example of making a
fault less severe – it could be retransmitted. The reader will probably realize that the techniques described for hiding failures are not guaranteed to work in the worst cases; for example, the data on the second disk may be corrupted too, or the message may not get through in a reasonable time however often it is retransmitted.
Tolerating failures: Most of the services
in the Internet do exhibit failures – it would not be practical for them to attempt to detect and hide all of the failures that might occur in such a large network with so many components. Their clients can be
designed to tolerate failures, which generally involves the users tolerating them as well. For example, when a web browser cannot contact a web server, it does not make the user wait 
for ever while it keeps on trying – it informs the user about the problem, leaving them free to try again later. Services that tolerate failures are discussed in the paragraph on redundancy below.
Recovery from failures: Recovery involves the design of software so that the state of permanent data can be recovered or ‘rolled back’ after a server has crashed. In general, the computations performed by some programs will be incomplete when a fault occurs, and the permanent data that they update (files and other material stored in permanent storage) may not be in a consistent state. 
Redundancy: Services can be made to tolerate failures by the use of redundant components. Consider the following examples:
1. There should always be at least two different routes between any two routers
in the Internet.
2. In the Domain Name System, every name table is replicated in at least two different servers.
3. A database may be replicated in several servers to ensure that the data remains accessible after the failure of any single server; the servers can be designed to detect faults in their peers; when a fault is detected in one server, clients are redirected to the remaining servers.
The design of effective techniques for keeping replicas of rapidly changing data up to-date without excessive loss of performance is a challenge. Approaches are discussed in Chapter 18.
Distributed systems provide a high degree of availability in the face of hardware faults.
The availability of a system is a measure of the proportion
of time that it is available for use. When one of the components in a distributed system fails, only the work that was using the failed component is affected. A user may move to another computer if the one that they were using fails; a server process can be started on another computer.
  

These Topics Are Also In Your Syllabus
1 Building the Baseline Project Plan link
2 Reviewing the Baseline Project Plan link
You May Find Something Very Interesting Here. link
3 Pine Valley Furniture WebStore: Systems Planning and Selection link
4 Performing Requirements Determination link
5 Traditional Methods for Determining Requirements link

Rating - 3/5
465 views

Advertisements
Rating - 3/5