consistent:保持弱一致性下的正确性和SLA

Subhajit Sidhanta, S. Mukhopadhyay, W. Golab
{"title":"consistent:保持弱一致性下的正确性和SLA","authors":"Subhajit Sidhanta, S. Mukhopadhyay, W. Golab","doi":"10.1145/3288599.3288630","DOIUrl":null,"url":null,"abstract":"While executing a client application, comprising a sequence of one or more storage operations (read, write, etc.), replicated datastores provide the option of tuning per-operation client-centric consistency settings, Weaker consistency settings allow client applications to execute with lower observed latency due to less coordination among the replica, improving throughput. To enable a client application running on a geo-replicated datastore to meet stringent SLA (Service Level Agreement) deadlines, i.e., latency thresholds provided in the SLA, users apply weak client-centric consistency settings. Strong consistency settings may result in higher latency due to coordination among greater number of replicas. However, since a weak consistency setting requires only a partial quorum of replicas to coordinate, some of the replicas may be overwritten by conflicting updates from concurrent clients, which, in turn, may result in violation of correctness conditions specified by the developer. Such correctness conditions are provided as postconditions that impose restrictions on the values observed by the clients. Enforcing correctness conditions under weak consistency settings on geo-replicated datastores from the client application code is a tedious and challenging task. The task is even more complicated when considering application-level SLA deadlines. Deadline (latency) is one of the most important SLA parameters for optimizing client-centric performance. To this end, we present Consistify, a novel framework, that acts as an interface layer between client applications and underlying data-stores, and enables client applications to execute with weak per-operation consistency settings, while simultaneously respecting: 1) the correctness conditions, specified using logical predicates, and 2) the SLA deadline. Using benchmark workloads, we experimentally demonstrate that Consistify outperforms the state-of-the-art systems, namely QUELA. For several other systems that provide flexible consistency settings, namely Bolt-on causal system, SIEVE, and Cure, we provide a comparison of the throughput and latency observed with Consistify against the numbers reported with those systems in prior papers.","PeriodicalId":346177,"journal":{"name":"Proceedings of the 20th International Conference on Distributed Computing and Networking","volume":"30 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2019-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"Consistify: preserving correctness and SLA under weak consistency\",\"authors\":\"Subhajit Sidhanta, S. Mukhopadhyay, W. Golab\",\"doi\":\"10.1145/3288599.3288630\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"While executing a client application, comprising a sequence of one or more storage operations (read, write, etc.), replicated datastores provide the option of tuning per-operation client-centric consistency settings, Weaker consistency settings allow client applications to execute with lower observed latency due to less coordination among the replica, improving throughput. To enable a client application running on a geo-replicated datastore to meet stringent SLA (Service Level Agreement) deadlines, i.e., latency thresholds provided in the SLA, users apply weak client-centric consistency settings. Strong consistency settings may result in higher latency due to coordination among greater number of replicas. However, since a weak consistency setting requires only a partial quorum of replicas to coordinate, some of the replicas may be overwritten by conflicting updates from concurrent clients, which, in turn, may result in violation of correctness conditions specified by the developer. Such correctness conditions are provided as postconditions that impose restrictions on the values observed by the clients. Enforcing correctness conditions under weak consistency settings on geo-replicated datastores from the client application code is a tedious and challenging task. The task is even more complicated when considering application-level SLA deadlines. Deadline (latency) is one of the most important SLA parameters for optimizing client-centric performance. To this end, we present Consistify, a novel framework, that acts as an interface layer between client applications and underlying data-stores, and enables client applications to execute with weak per-operation consistency settings, while simultaneously respecting: 1) the correctness conditions, specified using logical predicates, and 2) the SLA deadline. Using benchmark workloads, we experimentally demonstrate that Consistify outperforms the state-of-the-art systems, namely QUELA. For several other systems that provide flexible consistency settings, namely Bolt-on causal system, SIEVE, and Cure, we provide a comparison of the throughput and latency observed with Consistify against the numbers reported with those systems in prior papers.\",\"PeriodicalId\":346177,\"journal\":{\"name\":\"Proceedings of the 20th International Conference on Distributed Computing and Networking\",\"volume\":\"30 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2019-01-04\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings of the 20th International Conference on Distributed Computing and Networking\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/3288599.3288630\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the 20th International Conference on Distributed Computing and Networking","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3288599.3288630","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 1

摘要

在执行包含一个或多个存储操作(读、写等)序列的客户端应用程序时,复制的数据存储提供了调优每个操作以客户端为中心的一致性设置的选项,较弱的一致性设置允许客户端应用程序以较低的观察延迟执行,因为副本之间的协调较少,从而提高了吞吐量。为了使运行在地理复制数据存储上的客户端应用程序能够满足严格的SLA(服务水平协议)截止日期,即SLA中提供的延迟阈值,用户可以应用以客户端为中心的弱一致性设置。强一致性设置可能会导致更高的延迟,因为在更多的副本之间进行协调。然而,由于弱一致性设置只需要副本的部分仲裁来协调,一些副本可能会被来自并发客户机的冲突更新覆盖,这反过来又可能导致违反开发人员指定的正确性条件。这种正确性条件作为后置条件提供,对客户机观察到的值施加限制。在客户端应用程序代码的地理复制数据存储上执行弱一致性设置下的正确性条件是一项乏味且具有挑战性的任务。在考虑应用程序级SLA截止日期时,任务甚至更加复杂。截止日期(延迟)是优化以客户端为中心的性能的最重要的SLA参数之一。为此,我们提出了一个新的框架Consistify,它充当客户端应用程序和底层数据存储之间的接口层,并使客户端应用程序能够以弱的操作一致性设置执行,同时遵守:1)使用逻辑谓词指定的正确性条件,以及2)SLA截止日期。使用基准测试工作负载,我们通过实验证明了consistent优于最先进的系统,即QUELA。对于提供灵活一致性设置的其他几个系统,即Bolt-on因果系统、SIEVE和Cure,我们将使用consistent观察到的吞吐量和延迟与之前论文中使用这些系统报告的数字进行了比较。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
Consistify: preserving correctness and SLA under weak consistency
While executing a client application, comprising a sequence of one or more storage operations (read, write, etc.), replicated datastores provide the option of tuning per-operation client-centric consistency settings, Weaker consistency settings allow client applications to execute with lower observed latency due to less coordination among the replica, improving throughput. To enable a client application running on a geo-replicated datastore to meet stringent SLA (Service Level Agreement) deadlines, i.e., latency thresholds provided in the SLA, users apply weak client-centric consistency settings. Strong consistency settings may result in higher latency due to coordination among greater number of replicas. However, since a weak consistency setting requires only a partial quorum of replicas to coordinate, some of the replicas may be overwritten by conflicting updates from concurrent clients, which, in turn, may result in violation of correctness conditions specified by the developer. Such correctness conditions are provided as postconditions that impose restrictions on the values observed by the clients. Enforcing correctness conditions under weak consistency settings on geo-replicated datastores from the client application code is a tedious and challenging task. The task is even more complicated when considering application-level SLA deadlines. Deadline (latency) is one of the most important SLA parameters for optimizing client-centric performance. To this end, we present Consistify, a novel framework, that acts as an interface layer between client applications and underlying data-stores, and enables client applications to execute with weak per-operation consistency settings, while simultaneously respecting: 1) the correctness conditions, specified using logical predicates, and 2) the SLA deadline. Using benchmark workloads, we experimentally demonstrate that Consistify outperforms the state-of-the-art systems, namely QUELA. For several other systems that provide flexible consistency settings, namely Bolt-on causal system, SIEVE, and Cure, we provide a comparison of the throughput and latency observed with Consistify against the numbers reported with those systems in prior papers.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
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学术文献互助群
群 号:481959085
Book学术官方微信