{"id":7837,"date":"2019-01-30T12:15:31","date_gmt":"2019-01-30T12:15:31","guid":{"rendered":"https:\/\/support.loginextsolutions.com\/?p=7837"},"modified":"2026-01-28T09:43:18","modified_gmt":"2026-01-28T09:43:18","slug":"fault-failure","status":"publish","type":"post","link":"https:\/\/support.loginextsolutions.com\/index.php\/2019\/01\/30\/fault-failure\/","title":{"rendered":"Failure Detection and Fault Tolerance at LogiNext"},"content":{"rendered":"\n\n\n\t
\n\n\t\t<\/i><\/span> Download PDF<\/a>\n\n\t<\/div>\n\n\n\n\n\n

LogiNext\u2019s production environment is robust and dependable. The implementation of the Fault Tolerance techniques is based on a circular chain reaction of Failure, Error and Fault.<\/p>\n

A failure is said to occur in a system when the system\u2019s environment observes an output from the system that does not conform to its specification. An error is the part of the system, e.g. one of its constituent (sub)systems, which is liable to lead to a failure. A fault is the adjudged cause of an error and may itself be the result of a failure. Hence, a fault causes an error that produces a failure, which subsequently may result to a fault, and so on.<\/p>\n

All the failures are assessed and handled effectively and the system reacts gracefully to any unexpected equipment or programming malfunction by using world class techniques to confront the faults and its consequences. This is achieved by:<\/p>\n

1. First detecting the errors in the system – This is achieved by enabling the constituents of LogiNext\u2019s environment to monitor other constituents for failure occurrences. By observing a failure, the monitoring subsystem can detect an error on the monitored subsystem.<\/p>\n

2. Restoring or Recovering the system or subsystem on which error was detected before it affects other parts of the system\u00a0 – This is achieved through a technique called checkpointing. In this technique, in order to enable the restoration of a subsystem after an error has been detected on it, appropriate information regarding the subsystem is saved at regular intervals of time. The appropriate information saved is a complete snapshot of the internal subsystem representation (i.e. the state of the subsystem). When a monitoring subsystem observes a failure on a monitored subsystem, it activates a mechanism that will use the last checkpoint of the latter subsystem in order to eliminate the error that led to the observed failure and restore the subsystem to an error-free state.<\/p>\n

3. Masking of the error occurrence by isolating the subsystem on which the error was detected and using some form of redundancy to deliver the expected output\u00a0 – When a monitoring subsystem observes a failure on a monitored subsystem, it does not let the erroneous behaviour of the latter subsystem affect any other parts of the overall system by using a some form of redundancy by spawning a duplicate of the failed subsystem to cover up for the observed failure.<\/p>\n

The decision to deploy the right fault tolerance mechanism is decided by LogiNext architecture based on number of factors that include – simultaneous errors that may occur, the design, space and time complexity of the fault tolerant mechanism and how these align with the requirements about the corresponding system qualities. However, the failure types that will be confronted by a system play a primary and decisive role in the selection of the fault tolerance techniques that can be applied to render the system fault tolerant. Different fault tolerance techniques are developed and deployed by LogiNext in order to deal with different failure types which may differ in all three means for error detection, recovery and masking.<\/p>\n

LogiNext has implemented the fault tolerance techniques that considers the below metrics –<\/p>\n