Skip to main content
Log in

Comparing redundancy models for high availability middleware

  • Published:
Computing Aims and scope Submit manuscript

Abstract

Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9

Similar content being viewed by others

Notes

  1. SAForum is a consortium of telecom and computing companies.

  2. The node refers to the server where the component is executed.

  3. A switchover is a more graceful way of failing over.

  4. In the DSPN description, we use the terms ‘place’ and ‘state’ interchangeably, though the technical term is ‘place’, sometimes the term ‘state’ conveys better the meaning.

  5. Note that the CPU consumption may differ depending on the streaming protocol, VLC offers the use of many protocols (HTTP, UDP, RTSP, etc.).

References

  1. Trivedi K, Ciardo G, Dasarathy B, Grottke M, Rindos A, Varshaw B (2008) Achieving and assuring high availability. IEEE International Symposium on Parallel and Distributed Processing, 2008, IPDPS 2008, pp 1–7, April 2008

  2. Service Availability Forum, Application Interface Specification. http://www.saforum.org

  3. Fault-Tolerant CORBA Specifications. http://www.omg.org/technology/documents/corba_spec_catalog.htm

  4. Service Availability Forum, Application Interface Specification. Availability Management Framework SAI-AIS-AMF-B.04.01. http://www.saforum.org

  5. Smith WE, Trivedi KS, Tomek LA, Ackaret J (2008) Availability analysis of blade server systems. IBM Sys J 47(4):621–640

    Article  Google Scholar 

  6. Salfner F, Wolter K (2009) A Petri net model for service availability in redundant computing systems. In: Proceedings of the 2009 winter simulation conference (WSC), pp 819–826, 13–16

  7. Grzech A, Swiatek P (2011) Complex Services Availability in Service Oriented Systems. In: 21st international conference on systems engineering (ICSEng), pp 227–232 (16–18 Aug. 2011)

  8. Wei Xie D, Hairong S, Yonghuan C, Trivedi KS (2003) Modeling of user perceived webserver availability. In: IEEE international conference on communications, 2003, ICC ’03, vol 3, pp 1796–1800 (11–15 May 2003)

  9. Wang D, Trivedi KS (2005) Modeling User-Perceived Service Availability. In: Malek M, Nett E, Suri N (eds) ISAS 2005, LNCS, vol 3694. Springer, Berlin, pp 107–122

  10. Ajmone M, Chiola G (1987) On Petri Nets with deterministic and exponentially distributed firing times. In: Rozenberg G (ed) Adv. In Petri Nets 1987, LNCS, vol 266. Springer, Berlin, pp 132–145

  11. Choi H, Kulkarni VG, Trivedi KS (1993) Transient analysis of deterministic and stochastic Petri nets. In: Ajmone Marsan M (ed) Application and theory of petri Nets 1993, LNCS, vol 691. Springer, Berlin, pp 166–185

  12. Kanso A, Toeroe M, Khendek F (2013) Configuration-based service availability analysis for middleware managed applications. In: Haugen Ø, Reed R, Reinhard G (eds) System Analysis and Modeling: theory and practice. Lecture notes in computer science, vol 7744. Springer, Berlin, Heidelberg, pp 229–248

  13. Mishra A, Kanso A (2012) Integration of the VideoLAN Client with OpenSAF: An Example. In: Toeroe M, Tam F (eds) Service availability: principles and practice, Chap 14. Wiley, NewYork

  14. VideoLAN Client. http://www.videolan.org/

  15. OpenSAF foundation. http://www.opensaf.org/

  16. Song YJ, Tobagus W, Raymakers J, Fox A Is MTTR More Important Than MTTF for Improving User-Perceived Availability? Computer Science Department, Stanford University. http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.88.182

  17. Lyu MR (2007) Software Reliability Engineering: A Roadmap. Future of software engineering, 2007 (FOSE ’07) pp 153–170 (23–25 May 2007)

  18. Shi J, Wang S, Shang Y (2008) Petri-nets Based Availability Model of Fault-Tolerant Server System. In: IEEE conference on robotics, automation and mechatronics, 2008. pp 444–449 (21–24 Sept. 2008)

  19. Volovoi V (2004) Modeling of system reliability using Petri-nets with aging tokens. Reliabil Eng Sys Safety 84(2):149–161

    Article  Google Scholar 

Download references

Acknowledgments

This work is partially supported by the Natural Sciences and Engineering Research Council of Canada (NSERC) and Ericsson Research.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Ali Kanso.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Kanso, A., Toeroe, M. & Khendek, F. Comparing redundancy models for high availability middleware. Computing 96, 975–993 (2014). https://doi.org/10.1007/s00607-013-0361-x

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00607-013-0361-x

Keywords

Mathematics Subject Classification

Navigation