Replica Management in Object-Based Systems

  • Katsuya Tanaka
  • Makoto Takizawa
Conference paper


Objects are replicated in order to increase reliability and availability of an object-based system. We discuss how to invoke methods on replicas of objects in a nested manner. If a method t is invoked on multiple replicas and each instance of t on the replicas invokes a method u on another object y, u may be performed multiple times on some replica of y and then the replica gets inconsistent, i.e. redundant invocations. In addition, if each instance of t issues a request to a quorum, more number of the replicas are manipulated than the quorum number of the method u, i.e. quorum explosion. We discuss an invocation protocol to resolve the redundant invocation and quorum explosion. We evaluate the protocol on how many replicas are manipulated and requests are issued.


Request Message Redundancy Factor Mobile Transaction Replica Management Lock Manage 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Ahamad, M., Dasgupta, P., LeBlanc R., and Wilkes, C. (1987): Fault Tolerant Computing in Object Based Distributed Operating Systems, Proc. 6th IEEE SRDS, 115–125.Google Scholar
  2. 2.
    Barrett, P. A., Hilborne, A. M., Bond, P. G., and Seaton, D. T. (1990): The Delta-4 Extra Performance Architecture, Proc. 20th Int’l Symp. on FTCS, 481–488.Google Scholar
  3. 3.
    Birman, K. P. and Joseph, T. A. (1987): Reliable Communication in the Presence of Failures, ACM TOCS, 5 (1), 47–76.CrossRefGoogle Scholar
  4. 4.
    Borg, A., Baumbach, J., and Glazer, S. (1983): A Message System Supporting Fault Tolerance, Proc. 9th ACM Symp. on Operating Sys. Principles, 27–39.Google Scholar
  5. 5.
    Carey, J. M. and Livny, M. (1991): Conflict Detection Tradeoffs for Replicated Data, ACM TODS, 16 (4), 703–746.CrossRefGoogle Scholar
  6. 6.
    Chevalier, P. -Y. (1992): A Replicated Object Server for a Distributed Object-Oriented System, Proc. IEEE SRDS, 4–11.Google Scholar
  7. 7.
    Garcia-Molina, H. and Barbara, D. (1985): How to Assign Votes in a Distributed System, JACM, 32 (4), 841–860.MathSciNetMATHCrossRefGoogle Scholar
  8. 8.
    Gifford, D. K. (1979): Weighted Voting for Replicated Data, Proc. 7th ACM Symp. on Operating Systems Principles, 150–159Google Scholar
  9. 9.
    Jing, J., Bukhres, O., and Elmagarmid, A. (1995): Distributed Lock Management for Mobile Transactions, Proc. IEEE ICDCS-15, 118–125.Google Scholar
  10. 10.
    Korth, H. F. (1983): Locking Primitives in a Database System, JACM, 30 (1), 55–79.MathSciNetMATHCrossRefGoogle Scholar
  11. 11.
    Powell, D., Chereque, M., and Drackley, D. (1991): Fault-Tolerance in Delta-4, ACM Operating System Review, 25 (2), 121–125.CrossRefGoogle Scholar
  12. 12.
    Silvano, M. and Douglas, C. S. (1997): Constructing Reliable Distributed Communication Systems with CORBA, IEEE Comm. Magazine, 35 (2), 56–60.CrossRefGoogle Scholar
  13. 13.
    Tanaka, K., Hasegawa, K., and Takizawa, M. (2000): Quorum-Based Replication in Object-Based Systems, Journal of Information Science and Engineering (JISE), 16, 317–331.Google Scholar
  14. 14.
    Tanaka, K. and Takizawa, M. (2000): Quorum-Based Replication of Objects, Proc. 3rd DEXA Int’l Workshop on Network-Based Information Systems (NBIS-3), 33–37.Google Scholar

Copyright information

© Springer Japan 2002

Authors and Affiliations

  • Katsuya Tanaka
    • 1
  • Makoto Takizawa
    • 1
  1. 1.Dept. of Computers and Systems EngineeringTokyo Denki UniversityJapan

Personalised recommendations