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

自稳定协议在最终一致键值存储中的优势:案例研究

Benefit of Self-Stabilizing Protocols in Eventually Consistent Key-Value Stores: A Case Study

Duong Nguyen, Sandeep S. Kulkarni, Ajoy K. Datta

摘要:

在本文中,我们专注于分布式程序的实现中使用的键值存储的节点的状态存储在一个复制和分区的数据存储,以提高性能和可靠性。这种算法的应用发生在天气监测,社交媒体等,我们认为,这些应用程序应该被设计为稳定,使他们从任意状态恢复到合法状态。具体来说,如果我们使用稳定算法,那么我们可以使用更有效的实现,提供最终一致性,而不是顺序一致性,其中数据存储的行为就像只有一个数据副本。我们发现,虽然最终一致性的使用导致一致性违反故障(cvf),其中一些节点执行其动作不正确,因为它依赖于旧版本的数据,所产生的协议的整体性能更好。我们使用实验分析来评估预期的改善。我们还确定了其他变化的稳定,可以提供额外的保证,在最终consistency.Finally的存在下,我们注意到,如果底层算法不稳定,即使是一个单一的\cvf可能会导致算法完全失败,从而使它不可能受益于这种方法。

英文摘要:

In this paper, we focus on the implementation of distributed programs in using a key-value store where the state of the nodes is stored in a replicated and partitioned data store to improve performance and reliability. Applications of such algorithms occur in weather monitoring, social media, etc. We argue that these applications should be designed to be stabilizing so that they recover from an arbitrary state to a legitimate state. Specifically, if we use a stabilizing algorithm then we can work with more efficient implementations that provide eventual consistency rather than sequential consistency where the data store behaves as if there is just one copy of the data. We find that, although the use of eventual consistency results in consistency violation faults (cvf) where some node executes its action incorrectly because it relies on an older version of the data, the overall performance of the resulting protocol is better. We use experimental analysis to evaluate the expected improvement. We also identify other variations of stabilization that can provide additional guarantees in the presence of eventual consistency.Finally, we note that if the underlying algorithm is not stabilizing, even a single \cvf may cause the algorithm to fail completely thereby making it impossible to benefit from this approach.

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

↑