Exploring versioned distributed arrays for resilience in scientific applications: global view resilience. (November 2017)

• Record Type: Journal Article
• Authors: Chien, A; Balaji, P; Dun, N; Fang, A; Fujita, H; Iskra, K; Rubenstein, Z; Zheng, Z; Hammond, J; Laguna, I; Richards, D; Dubey, A; van Straalen, B; Hoemmen, M; Heroux, M; Teranishi, K; Siegel, A
• Is Part Of: International journal of high performance computing applications. Volume 31:Number 6(2017)
• Page Start: 564
• Page End: 590
• Publication Date: 2017-11
• Subjects: Resilience -- fault-tolerance -- exascale -- scalable computing -- application-based fault tolerance; High performance computing -- Periodicals; Supercomputers -- Periodicals; 004.1105
• DOI: 10.1177/1094342016664796
• Languages: English
• ISSNs: 1094-3420

Abstract

Exascale studies project reliability challenges for future HPC systems. We present the Global View Resilience (GVR) system, a library for portable resilience. GVR begins with a subset of the Global Arrays interface, and adds new capabilities to create versions, name versions, and compute on version data. Applications can focus versioning where and when it is most productive, and customize for each application structure independently. This control is portable, and its embedding in application source makes it natural to express and easy to maintain. The ability to name multiple versions and "partially materialize" them efficiently makes ambitious forward-recovery based on "data slices" across versions or data structures both easy to express and efficient. Using several large applications (OpenMC, preconditioned conjugate gradient (PCG) solver, ddcMD, and Chombo), we evaluate the programming effort to add resilience. The required changes are small (< 2% lines of code (LOC)), localized and machine-independent, and perhaps most important, require no software architecture changes. We also measure the overhead of adding GVR versioning and show that overheads < 2% are generally achieved. This overhead suggests that GVR can be implemented in large-scale codes and support portable error recovery with modest investment and runtime impact. Our results are drawn from both IBM BG/Q and Cray XC30 experiments, demonstrating portability. We also present two case studies of flexible error recovery, illustrating how GVR can be used for multi-version rollback recovery, and several different forward-recovery schemes. GVR's multi-version enables applications to survive latent errors (silent data corruption) with significant detection latency, and forward recovery can make that recovery extremely efficient. Our results suggest that GVR is scalable, portable, and efficient. GVR interfaces are flexible, supporting a variety of recovery schemes, and altogether GVR embodies a gentle-slope path to tolerate growing error rates in future extreme-scale systems.