# 위키피디아
Crash-only software refers to computer programs that handle failures by simply restarting, without attempting any sophisticated recovery. Correctly written components of crash-only software can microreboot to a known-good state without the help of a user. Since failure-handling and normal startup use the same methods, this can increase the chance that bugs in failure-handling code will be noticed, except when there are leftover artifacts, such as data corruption from a severe failure, that don't occur during normal startup.
http://en.wikipedia.org/wiki/Crash-only_software
# Original paper
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 components, and the use of transparent component-level
retries hides intra-system component crashes from end users.
http://dslab.epfl.ch/pubs/crashonly/
Crash-only software refers to computer programs that handle failures by simply restarting, without attempting any sophisticated recovery. Correctly written components of crash-only software can microreboot to a known-good state without the help of a user. Since failure-handling and normal startup use the same methods, this can increase the chance that bugs in failure-handling code will be noticed, except when there are leftover artifacts, such as data corruption from a severe failure, that don't occur during normal startup.
http://en.wikipedia.org/wiki/Crash-only_software
# Original paper
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 components, and the use of transparent component-level
retries hides intra-system component crashes from end users.
http://dslab.epfl.ch/pubs/crashonly/
댓글 없음:
댓글 쓰기