Imperial College London

ProfessorNobukoYoshida

Faculty of EngineeringDepartment of Computing

Academic Visitor
 
 
 
//

Contact

 

+44 (0)20 7594 8240n.yoshida Website

 
 
//

Location

 

556Huxley BuildingSouth Kensington Campus

//

Summary

 

Publications

Citation

BibTex format

@inproceedings{Neykova:2017:10.1145/3033019.3033031,
author = {Neykova, R and Yoshida, N},
doi = {10.1145/3033019.3033031},
pages = {98--108},
publisher = {ACM},
title = {Let it recover: multiparty protocol-induced recovery},
url = {http://dx.doi.org/10.1145/3033019.3033031},
year = {2017}
}

RIS format (EndNote, RefMan)

TY  - CPAPER
AB - Fault-tolerant communication systems rely on recovery strategieswhich are often error-prone (e.g. a programmer manually specifiesrecovery strategies) or inefficient (e.g. the whole system is restartedfrom the beginning). This paper proposes a static analysis based onmultiparty session types that can efficiently compute a safe globalstate from which a system of interacting processes should be recov-ered. We statically analyse the communication flow of a program,given as a multiparty protocol, to extract the causal dependenciesbetween processes and to localise failures. We formalise our re-covery algorithm and prove its safety. A recovered communicationsystem is free from deadlocks, orphan messages and reception er-rors. Our recovery algorithm incurs less communication cost (onlyaffected processes are notified) and overall execution time (onlyrequired states are repeated). On top of our analysis, we designand implement a runtime framework in Erlang where failed pro-cesses and their dependencies are soundly restarted from a com-puted safe state. We evaluate our recovery framework on message-passing benchmarks and a use case for crawling webpages. Theexperimental results indicate our framework outperforms a built-instatic recovery strategy in Erlang when a part of the protocol canbe safely recovered.
AU - Neykova,R
AU - Yoshida,N
DO - 10.1145/3033019.3033031
EP - 108
PB - ACM
PY - 2017///
SP - 98
TI - Let it recover: multiparty protocol-induced recovery
UR - http://dx.doi.org/10.1145/3033019.3033031
UR - http://hdl.handle.net/10044/1/43566
ER -