arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 2207.02746cs.DB
收藏

C5:始终保持运行的克隆并发控制

C5: Cloned Concurrency Control that Always Keeps Up

Jeffrey Helt, Abhinav Sharma, Daniel J. Abadi, Wyatt Lloyd, Jose M. Faleiro

摘要:

通常部署异步复制的主备份数据库以提高可用性并卸载只读事务。为了应用从主服务器复制的写入并服务只读事务,备份服务器实现克隆的并发控制协议。该协议确保只读事务始终返回主服务器上先前存在的状态的快照。这迫使备份精确地复制由主服务器的并发控制产生的提交顺序。现有的克隆并发控制协议通过限制备份的并行性来保证这一点。因此,主服务器的并发控制执行某些工作负载时的并行性要高于这些协议。在本文中,我们证明了这种并行差距导致无限的复制滞后,写入可以采取任意长的时间复制到备份,并导致灾难性的故障,在生产系统。然后,我们设计C5,第一个克隆并发协议,提供有限的复制滞后。我们实现了两个版本的C5:我们的评估MyRocks,一个广泛部署的数据库,证明C5提供了有限的复制滞后。我们在最近的内存数据库Cicada中的评估表明,C5甚至可以跟上最快的初选。

英文摘要:

Asynchronously replicated primary-backup databases are commonly deployed to improve availability and offload read-only transactions. To both apply replicated writes from the primary and serve read-only transactions, the backups implement a cloned concurrency control protocol. The protocol ensures read-only transactions always return a snapshot of state that previously existed on the primary. This compels the backup to exactly copy the commit order resulting from the primary's concurrency control. Existing cloned concurrency control protocols guarantee this by limiting the backup's parallelism. As a result, the primary's concurrency control executes some workloads with more parallelism than these protocols. In this paper, we prove that this parallelism gap leads to unbounded replication lag, where writes can take arbitrarily long to replicate to the backup and which has led to catastrophic failures in production systems. We then design C5, the first cloned concurrency protocol to provide bounded replication lag. We implement two versions of C5: Our evaluation in MyRocks, a widely deployed database, demonstrates C5 provides bounded replication lag. Our evaluation in Cicada, a recent in-memory database, demonstrates C5 keeps up with even the fastest of primaries.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑