Transactional failure recovery for a distributed key-value store

Ahmad, Muhammad Yousuf and Kemme, Bettina and Brondino, Ivan and Patiño-Martínez, Marta and Jiménez-Peris, Ricardo (2013). Transactional failure recovery for a distributed key-value store. In: "ACM/IFIP/USENIX 14th International Middleware Conference, Beijing, China, December 9-13, 2013, Proceedings", 09-13 Dic 2013, Beijing, China. ISBN 978-3-642-45064-8. pp. 267-286. https://doi.org/10.1007/978-3-642-45065-5_14.

Description

Title: Transactional failure recovery for a distributed key-value store
Author/s:
  • Ahmad, Muhammad Yousuf
  • Kemme, Bettina
  • Brondino, Ivan
  • Patiño-Martínez, Marta
  • Jiménez-Peris, Ricardo
Item Type: Presentation at Congress or Conference (Article)
Event Title: ACM/IFIP/USENIX 14th International Middleware Conference, Beijing, China, December 9-13, 2013, Proceedings
Event Dates: 09-13 Dic 2013
Event Location: Beijing, China
Title of Book: Middleware 2013
Date: 2013
ISBN: 978-3-642-45064-8
Volume: 8275
Subjects:
Faculty: Facultad de Informática (UPM)
Department: Lenguajes y Sistemas Informáticos e Ingeniería del Software
Creative Commons Licenses: Recognition - No derivative works - Non commercial

Full text

[img]
Preview
PDF - Requires a PDF viewer, such as GSview, Xpdf or Adobe Acrobat Reader
Download (1MB) | Preview

Abstract

With the advent of cloud computing, many applications have embraced the ensuing paradigm shift towards modern distributed key-value data stores, like HBase, in order to benefit from the elastic scalability on offer. However, many applications still hesitate to make the leap from the traditional relational database model simply because they cannot compromise on the standard transactional guarantees of atomicity, isolation, and durability. To get the best of both worlds, one option is to integrate an independent transaction management component with a distributed key-value store. In this paper, we discuss the implications of this approach for durability. In particular, if the transaction manager provides durability (e.g., through logging), then we can relax durability constraints in the key-value store. However, if a component fails (e.g., a client or a key-value server), then we need a coordinated recovery procedure to ensure that commits are persisted correctly. In our research, we integrate an independent transaction manager with HBase. Our main contribution is a failure recovery middleware for the integrated system, which tracks the progress of each commit as it is flushed down by the client and persisted within HBase, so that we can recover reliably from failures. During recovery, commits that were interrupted by the failure are replayed from the transaction management log. Importantly, the recovery process does not interrupt transaction processing on the available servers. Using a benchmark, we evaluate the impact of component failure, and subsequent recovery, on application performance.

More information

Item ID: 25923
DC Identifier: http://oa.upm.es/25923/
OAI Identifier: oai:oa.upm.es:25923
DOI: 10.1007/978-3-642-45065-5_14
Official URL: http://link.springer.com/chapter/10.1007%2F978-3-642-45065-5_14
Deposited by: Memoria Investigacion
Deposited on: 09 Jun 2014 09:38
Last Modified: 04 Dec 2017 11:01
  • Logo InvestigaM (UPM)
  • Logo GEOUP4
  • Logo Open Access
  • Open Access
  • Logo Sherpa/Romeo
    Check whether the anglo-saxon journal in which you have published an article allows you to also publish it under open access.
  • Logo Dulcinea
    Check whether the spanish journal in which you have published an article allows you to also publish it under open access.
  • Logo de Recolecta
  • Logo del Observatorio I+D+i UPM
  • Logo de OpenCourseWare UPM