Revision as of 17:55, 15 April 2018 edit 171.48.62.221 (talk) →Synchronous duplex mode ← Previous edit		Revision as of 03:58, 19 April 2018 edit undo Jim.henderson (talk \| contribs) Autopatrolled, Event coordinators, Extended confirmed users, IP block exemptions, Pending changes reviewers, Rollbackers 73,294 edits →Synchronous duplex mode: Distinguish between transient and hard faults Tag: Visual edit Next edit →
Line 61: It is possible that a comparator fault occurs only due to transient failure which is not shown even when check out program is run. In such case three possibilities exists: Continue with both processors #Continue with both processors #Take out the active processor and continue with the other. *#Continue with active processor but remove other processor from service. ~~This~~The ~~scheme~~first is based on the assumption that the fault is transient one and may not appear again. ~~Here~~In the other cases, the processor taken out is subjected to extensive testing to identify a marginal failure ~~in these cases~~. ====Load-sharing mode====

Stored program control: Difference between revisions