MPI Stages: Checkpointing MPI State for Bulk Synchronous Applications

Nawrin Sultana, A. Skjellum, I. Laguna, M. Farmer, K. Mohror, M. Emani
{"title":"MPI Stages: Checkpointing MPI State for Bulk Synchronous Applications","authors":"Nawrin Sultana, A. Skjellum, I. Laguna, M. Farmer, K. Mohror, M. Emani","doi":"10.1145/3236367.3236385","DOIUrl":null,"url":null,"abstract":"When an MPI program experiences a failure, the most common recovery approach is to restart all processes from a previous checkpoint and to re-queue the entire job. A disadvantage of this method is that, although the failure occurred within the main application loop, live processes must start again from the beginning of the program, along with new replacement processes---this incurs unnecessary overhead for live processes. To avoid such overheads and concomitant delays, we introduce the concept of \"MPI Stages.\" MPI Stages saves internal MPI state in a separate checkpoint in conjunction with application state. Upon failure, both MPI and application state are recovered, respectively, from their last synchronous checkpoints and continue without restarting the overall MPI job. Live processes roll back only a few iterations within the main loop instead of rolling back to the beginning of the program, while a replacement of failed process restarts and reintegrates, thereby achieving faster failure recovery. This approach integrates well with large-scale, bulk synchronous applications and checkpoint/restart. In this paper, we identify requirements for production MPI implementations to support state checkpointing with MPI Stages, which includes capturing and managing internal MPI state and serializing and deserializing user handles to MPI objects. We evaluate our fault tolerance approach with a proof-of-concept prototype MPI implementation that includes MPI Stages. We demonstrate its functionality and performance using LULESH and microbenchmarks. Our results show that MPI Stages reduces the recovery time by 13× for LULESH in comparison to checkpoint/restart.","PeriodicalId":225539,"journal":{"name":"Proceedings of the 25th European MPI Users' Group Meeting","volume":"38 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2018-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"11","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the 25th European MPI Users' Group Meeting","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3236367.3236385","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 11

Abstract

When an MPI program experiences a failure, the most common recovery approach is to restart all processes from a previous checkpoint and to re-queue the entire job. A disadvantage of this method is that, although the failure occurred within the main application loop, live processes must start again from the beginning of the program, along with new replacement processes---this incurs unnecessary overhead for live processes. To avoid such overheads and concomitant delays, we introduce the concept of "MPI Stages." MPI Stages saves internal MPI state in a separate checkpoint in conjunction with application state. Upon failure, both MPI and application state are recovered, respectively, from their last synchronous checkpoints and continue without restarting the overall MPI job. Live processes roll back only a few iterations within the main loop instead of rolling back to the beginning of the program, while a replacement of failed process restarts and reintegrates, thereby achieving faster failure recovery. This approach integrates well with large-scale, bulk synchronous applications and checkpoint/restart. In this paper, we identify requirements for production MPI implementations to support state checkpointing with MPI Stages, which includes capturing and managing internal MPI state and serializing and deserializing user handles to MPI objects. We evaluate our fault tolerance approach with a proof-of-concept prototype MPI implementation that includes MPI Stages. We demonstrate its functionality and performance using LULESH and microbenchmarks. Our results show that MPI Stages reduces the recovery time by 13× for LULESH in comparison to checkpoint/restart.
MPI阶段:批量同步应用程序的MPI状态检查点
当MPI程序出现故障时,最常见的恢复方法是从以前的检查点重新启动所有进程,并重新为整个作业排队。这种方法的缺点是,尽管故障发生在主应用程序循环中,但活动进程必须从程序的开始重新启动,并伴随着新的替换进程——这为活动进程带来了不必要的开销。为了避免此类开销和伴随的延迟,我们引入了“MPI阶段”的概念。MPI Stages将内部MPI状态与应用程序状态一起保存在一个单独的检查点中。在发生故障时,MPI和应用程序状态分别从它们的最后一个同步检查点恢复,并且在不重新启动整个MPI作业的情况下继续运行。活动流程只回滚主循环中的几个迭代,而不是回滚到程序的开始,而失败流程的替换将重新启动并重新集成,从而实现更快的故障恢复。这种方法可以很好地集成大规模、批量同步应用程序和检查点/重启。在本文中,我们确定了生产MPI实现的需求,以支持MPI阶段的状态检查点,其中包括捕获和管理内部MPI状态,以及对MPI对象的用户句柄进行序列化和反序列化。我们通过包括MPI阶段的概念验证原型MPI实现来评估我们的容错方法。我们使用LULESH和微基准测试来演示其功能和性能。我们的研究结果表明,与检查点/重启相比,MPI阶段将LULESH的恢复时间减少了13倍。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信