Challenges in Developing MPI Fault-Tolerant Fortran Applications

Weeks, Nathan T.; Luecke, Glenn R.; Maris, Pieter; Vary, James P.

doi:10.1109/cluster.2018.00068

Cited by 2 publications

(1 citation statement)

References 28 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The MPI version of the NAS CG benchmark is available in Fortran. While the preferred option for us would be to only make incremental changes to the original Fortran code, various challenges have been reported when using ULFM with Fortran applications (see Weeks et al [23]). Therefore, despite the effort, we decided to port the MPI version from Fortran to C.…”

Section: Extensions To Cg and Lulesh 71 Cg From Nas Parallel Benchmarksmentioning

confidence: 99%

Implementing efficient message logging protocols as MPI application extensions

Dichev

Nikolopoulos

2019

Proceedings of the 26th European MPI Users' Group Meeting

View full text Add to dashboard Cite

Message logging protocols are enablers of local rollback, a more efficient alternative to global rollback, for fault tolerant MPI applications. Until now, message logging MPI implementations have incurred the overheads of a redesign and redeployment of an MPI library, as well as continued performance penalties across various kernels. Successful research efforts for message logging implementations do exist, but not a single one of them can be easily deployed today by more than a few experts. In contrast, in this work we build efficient message logging capabilities on top of an MPI library with no message logging capabilities; we do so for two different HPC kernels, one with a global exchange pattern (CG), and one with a neighbourhood exchange pattern (LULESH). While our library of choice ULFM detects failure and recovers MPI communicators, we build on that to then restore the intra-and inter-process data consistency of both applications. This task turns out to be challenging, and we present the methodology for doing so in this work. In the end, we achieve message logging capabilities for each kernel, without the need for an actual message logging runtime underneath. On the performance side, we match state-of-the-art solutions and (a) eliminate event logging and the event logger component altogether, and (b) design a hybrid protocol, which gracefully shifts between global and local rollback, depending on the available payload logging memory. Such a hybrid protocol between local and global rollback has not been previously proposed to our knowledge. Our extensions span a few hundred lines of code for each kernel, are open-sourced, and enable local and global rollback after process failure.

show abstract

Section: Extensions To Cg and Lulesh 71 Cg From Nas Parallel Benchmarksmentioning

confidence: 99%