Alleviating File System Journaling Problem in Containers for DBMS Consolidation

Asraa ABDULRAZAK ALI MARDAN; Kenji KONO

doi:10.1587/transinf.2020EDP7178

Alleviating File System Journaling Problem in Containers for DBMS Consolidation

Asraa ABDULRAZAK ALI MARDAN, Kenji KONO

Full Text Views

0

Cite this

Summary :

Containers offer a lightweight alternative over virtual machines and become a preferable choice for application consolidation in the clouds. However, the sharing of kernel components can violate the I/O performance and isolation in containers. It is widely recognized that file system journaling has terrible performance side effects in containers, especially when consolidating database management systems (DBMSs). The sharing of journaling modules among containers causes performance dependency among them. This dependency violates resource consumption enforced by the resource controller, and degrades I/O performance due to the contention of the journaling module. The operating system developers have been working on novel designs of file systems or new journaling mechanisms to solve the journaling problems. This paper shows that it is possible to overcome journaling problems without re-designing file systems or implementing a new journaling method. A careful configuration of containers in existing file systems can gracefully solve the problems. Our recommended configuration consists of 1) per-container journaling by presenting each container with a virtual block device to have its own journaling module, and 2) accounting journaling I/Os separately for each container. Our experimental results show that our configuration resolves journaling-related problems, improves MySQL performance by 3.4x, and achieves reasonable performance isolation among containers.

Publication: IEICE TRANSACTIONS on Information Vol.E104-D No.7 pp.931-940

Publication Date: 2021/07/01

Publicized: 2021/04/01

Online ISSN: 1745-1361

DOI: 10.1587/transinf.2020EDP7178

Type of Manuscript: PAPER

Category: Software System

Cite this

Copy

Asraa ABDULRAZAK ALI MARDAN, Kenji KONO, "Alleviating File System Journaling Problem in Containers for DBMS Consolidation" in IEICE TRANSACTIONS on Information, vol. E104-D, no. 7, pp. 931-940, July 2021, doi: 10.1587/transinf.2020EDP7178.
Abstract: Containers offer a lightweight alternative over virtual machines and become a preferable choice for application consolidation in the clouds. However, the sharing of kernel components can violate the I/O performance and isolation in containers. It is widely recognized that file system journaling has terrible performance side effects in containers, especially when consolidating database management systems (DBMSs). The sharing of journaling modules among containers causes performance dependency among them. This dependency violates resource consumption enforced by the resource controller, and degrades I/O performance due to the contention of the journaling module. The operating system developers have been working on novel designs of file systems or new journaling mechanisms to solve the journaling problems. This paper shows that it is possible to overcome journaling problems without re-designing file systems or implementing a new journaling method. A careful configuration of containers in existing file systems can gracefully solve the problems. Our recommended configuration consists of 1) per-container journaling by presenting each container with a virtual block device to have its own journaling module, and 2) accounting journaling I/Os separately for each container. Our experimental results show that our configuration resolves journaling-related problems, improves MySQL performance by 3.4x, and achieves reasonable performance isolation among containers.
URL: https://global.ieice.org/en_transactions/information/10.1587/transinf.2020EDP7178/_p

Copy

@ARTICLE{e104-d_7_931,
author={Asraa ABDULRAZAK ALI MARDAN, Kenji KONO, },
journal={IEICE TRANSACTIONS on Information},
title={Alleviating File System Journaling Problem in Containers for DBMS Consolidation},
year={2021},
volume={E104-D},
number={7},
pages={931-940},
abstract={Containers offer a lightweight alternative over virtual machines and become a preferable choice for application consolidation in the clouds. However, the sharing of kernel components can violate the I/O performance and isolation in containers. It is widely recognized that file system journaling has terrible performance side effects in containers, especially when consolidating database management systems (DBMSs). The sharing of journaling modules among containers causes performance dependency among them. This dependency violates resource consumption enforced by the resource controller, and degrades I/O performance due to the contention of the journaling module. The operating system developers have been working on novel designs of file systems or new journaling mechanisms to solve the journaling problems. This paper shows that it is possible to overcome journaling problems without re-designing file systems or implementing a new journaling method. A careful configuration of containers in existing file systems can gracefully solve the problems. Our recommended configuration consists of 1) per-container journaling by presenting each container with a virtual block device to have its own journaling module, and 2) accounting journaling I/Os separately for each container. Our experimental results show that our configuration resolves journaling-related problems, improves MySQL performance by 3.4x, and achieves reasonable performance isolation among containers.},
keywords={},
doi={10.1587/transinf.2020EDP7178},
ISSN={1745-1361},
month={July},}

Copy

TY - JOUR
TI - Alleviating File System Journaling Problem in Containers for DBMS Consolidation
T2 - IEICE TRANSACTIONS on Information
SP - 931
EP - 940
AU - Asraa ABDULRAZAK ALI MARDAN
AU - Kenji KONO
PY - 2021
DO - 10.1587/transinf.2020EDP7178
JO - IEICE TRANSACTIONS on Information
SN - 1745-1361
VL - E104-D
IS - 7
JA - IEICE TRANSACTIONS on Information
Y1 - July 2021
AB - Containers offer a lightweight alternative over virtual machines and become a preferable choice for application consolidation in the clouds. However, the sharing of kernel components can violate the I/O performance and isolation in containers. It is widely recognized that file system journaling has terrible performance side effects in containers, especially when consolidating database management systems (DBMSs). The sharing of journaling modules among containers causes performance dependency among them. This dependency violates resource consumption enforced by the resource controller, and degrades I/O performance due to the contention of the journaling module. The operating system developers have been working on novel designs of file systems or new journaling mechanisms to solve the journaling problems. This paper shows that it is possible to overcome journaling problems without re-designing file systems or implementing a new journaling method. A careful configuration of containers in existing file systems can gracefully solve the problems. Our recommended configuration consists of 1) per-container journaling by presenting each container with a virtual block device to have its own journaling module, and 2) accounting journaling I/Os separately for each container. Our experimental results show that our configuration resolves journaling-related problems, improves MySQL performance by 3.4x, and achieves reasonable performance isolation among containers.
ER -