The ISTORE Approach
Divides self-maintenance into two components:
1) reactive self-maintenance: dynamic reaction to exceptional system events
- self-diagnosing, self-monitoring hardware
- software monitoring and problem detection
- automatic reaction to detected problems
2) proactive self-maintenance: continuous online self- testing and self-analysis
- in situ fault injection, self-testing, and scrubbing to detect flaky hardware components and to exercise rarely-taken application code paths before they’re used
- automatic characterization of system components