期刊文献+

一种复制数据库恢复协议研究

On a Recovery Protocol for Replicated Databases
下载PDF
导出
摘要 数据复制是提高数据库系统性能和可用性的重要技术。近年来出现的基于组通信技术的数据库复制协议较之传统的数据库复制协议因其实现简单灵活、性能较优,在构建实用复制数据库系统时得到广泛应用。维持各节点副本一致性是数据复制技术研究的核心问题。本文讨论了当故障节点恢复后重新加入系统或增加新节点后如何恢复、维护系统节点副本间的一致性的问题。本文提出了一个针对分布复制数据库系统的恢复协议,该协议结合基于组通信技术的复制协议,可在不影响系统正常事务处理的情况下,实现故障恢复后节点或全新节点重新加入系统时的系统正确恢复,并给出了理论证明。同时还证明,该恢复协议对于分布在不可靠网络上的复制数据库的恢复问题同样适用。 Database replication is a well-known technique for increasing performance (response time, throughput, etc. ) and availability in distributed databases. Over the past few years, a database replication protocol based on group communication has been widely used in constructing practical replicated databases for its advantages in easier and more flexible implementation with good performance compared to traditional replication protocols. To keep the consistency of all replicas on sites is a key problem of the research in database replication. This paper discusses the problem of how to regain the consistency of replicas after the recovery of the failed sites or adding new sites. A recovery protocol for distributed replicated databases is provided. Combined with the replication protocol based on group communication, the protocol can make the replicated system recover correctly after a site, which is completely new or has recovered from a failure, rejoining the system, while the whole system can still process transactions without being interrupted. We give a theoretical correctness proof of it, and also prove that it is suitable for the replicated databases which are distributed on an unreliable network
出处 《计算机工程与科学》 CSCD 2008年第8期100-104,共5页 Computer Engineering & Science
基金 国家863计划资助项目(2006AA01Z451 2006AA10Z237) 教育部新世纪优秀人才支持计划资助项目(NCET)
关键词 数据库复制 数据库恢复 组通信 database replication database recovery group communication
  • 相关文献

参考文献9

  • 1Gray J, Helland P, O'Neil P, et al. The Dangers of Replication and a Solution[C]//Proc of SIGMOD'96,1996 : 173-182.
  • 2Kemme B, Pedone F, Alonso G, et al. Using Optimistic Atomic Broadcast in Transaction Processing Systems[J]. IEEE Trans on Knowledge Data Engineering, 2003, 15(4): 1018-1032.
  • 3Kemme B,Alonso G. Don't Be Lazy, Be Consistent.. Postgres-R, A New Way to Implement Database Repllcatlon[C] //Proc of the Int'l Conf on Very Large Databases, 2000. 134-143.
  • 4Patino-Martinez M, Jimenez R, Kemme B, et al. Consistent Database Replication at the Middleware Level [J]. ACM Trans on Computer Systems, 2005,23(4) :375-423.
  • 5Armendariz-Inigo J E, Decker H, de Mendivil J R G. Middleware-Based Data Replication: Some History and Future Trends[C]//Proc of the 17th Int'l Conf on Database and Expert Systems Applications, 2006: 390-394.
  • 6Kemme B, Bartoli A, Babaoglu O. Online Reconfiguration in Replicated Databases Based on Group Communication[C]// Proc of the Int'l Conf on Dependable Systems and Networks, 2001.
  • 7Wu S,Kemme B. Postgres-R (SI).. Combining Replica Control with Concurrency Control Based on Snapshot Isolation [C]//Proc of the 21st Int'l Conf on Data Engineering, 2005: 422-433.
  • 8Armendariz-Inigo J E, Garitagoitia J R, Munoz-Eseoi F D, et al. MADIS-SI; A Database Replication Protocol with Easy Recovery [ R]. Technical Report ITI-ITE-06/05, Institute Tecnologico de Informatica, Universidad Politecnica de Valencia, 2006.
  • 9Armendariz J E, Munoz F D, Ruiz M I, et al. Dealing with Writeset Conflicts in Database Replication Middlewares[R]. Technical Report ITI-ITE-05/11, Institute Tecnologieo de Informatica, Universidad Politecnica de Valencia, 2005.

相关作者

内容加载中请稍等...

相关机构

内容加载中请稍等...

相关主题

内容加载中请稍等...

浏览历史

内容加载中请稍等...
;
使用帮助 返回顶部