George Candea and Armando Fox. Crash-only software. In Proc. 9th Workshop on Hot Topics in Operating Systems, Lihue, HI, June 2003. @ NUS Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Combining Statistical Monitoring and Predictable - Recovery For Self-Management Self-citation (Fox) (Correct)
No context found.
George Candea and Armando Fox. Crash-only software. In Proc. 9th Workshop on Hot Topics in Operating Systems, Lihue, HI, June 2003.
Microreboot - A Technique for Cheap Recovery - Candea, Kawamoto, Fujiki.. (2004) (4 citations) Self-citation (Candea Fox) (Correct)
No context found.
G. Candea and A. Fox. Crash-only software. In Proc. 9th Workshop on Hot Topics in Operating Systems, Lihue, Hawaii, 2003.
Statistical Monitoring + Predictable Recovery = Self-* - Armando Fox And Self-citation (Fox) (Correct)
No context found.
George Candea and Armando Fox. Crash-only software. In Proc. 9th Workshop on Hot Topics in Operating Systems, Lihue, HI, June 2003.
Session State: Beyond Soft State - Benjamin Ling Emre (2004) (3 citations) Self-citation (Fox) (Correct)
No context found.
G. Candea and A. Fox. Crash-only software. In Proc. 9th Workshop on Hot Topics in Operating Systems, Lihue, HI, June 2003.
Session State: Beyond Soft State - Benjamin Ling Emre (2004) (3 citations) Self-citation (Fox) (Correct)
No context found.
George Candea and Armando Fox. Crash-only software. In Proc. 9th Workshop on Hot Topics in Operating Systems, Lihue, HI, June 2003.
Improving Availability with Recursive Micro-Reboots: A.. - Candea, Cutler, Fox (2003) (1 citation) Self-citation (Candea Fox) (Correct)
....VM can inspect the application s use of synchronization primitives. Placing timeouts on all communication enables the detection of remote failures, and using ICMP pings can reveal network partitions. Monitoring application activity in terms of I O and communication can also help infer progress [20]. Application level monitoring uses a combination of application progress counters and behavior monitors. The counters are component implemented methods that translate application specific progress into a universal number (e.g. a distributed transaction manager engaged in a 2 phase commit ....
....recovery can accomodate a wider range of recovery semantics for the cases where systems have hard state, we believe that using a uniform recovery strategy is very appealing both from an implementation and administration point of view. We have therefore developed the notion of crash only software [20], which we summarize in the following section. 4 Crash Only Software Crash only programs crash safely and recover quickly. There is only one way to stop such software by crashing it and only one way to bring it up by initiating recovery. Crash only systems are built from crash only ....
[Article contains additional citation context not shown here]
G. Candea and A. Fox. Crash-only software. In Proc. 9th Workshop on Hot Topics in Operating Systems, Lihue, Hawaii, 2003.
Building a Reactive Immune System for Software Services - Sidiroglou, Locasto.. (2004) (5 citations) (Correct)
No context found.
G. Candea and A. Fox. Crash-only software. In Proceedings of the 9th Workshop on Hot Topics in Operating Systems, May 2003.
Flashback: A Lightweight Extension for Rollback and .. - Srinivasan.. (2004) (1 citation) (Correct)
No context found.
G. Candea and A. Fox. Crashonly software. In Proceedings of the 9th Workshop on Hot Topics in Operating Systems, May 2003.
Nonintrusive Failure Detection and Recovery for.. - Sultan, Bohra.. (Correct)
No context found.
G. Candea and A. Fox. Crash-Only Software. In HotOS IX, May 2003.
Online articles have much greater impact More about CiteSeer.IST at NUS Add search form to your site Submit documents Feedback
CiteSeer.IST at NUS - Copyright Penn State and NEC. Hosted by the School of Computing, National University of Singapore.