Corosync Cluster Engine

Last updated

Developer(s) The Corosync Development Community
Initial release2008;17 years ago (2008)
Stable release
3.1.9 [1]   OOjs UI icon edit-ltr-progressive.svg () / 15 November 2024
Repository
Written in C
Operating system Cross-platform
Type Group Communication System
License New BSD License
Website corosync.github.io

The Corosync Cluster Engine is an open source implementation of the Totem Single Ring Ordering and Membership protocol. It was originally derived from the OpenAIS project and licensed under the new BSD License. The mission of the Corosync effort is to develop, release, and support a community-defined, open source cluster.

Contents

Features

The Corosync Cluster Engine is a group communication system with additional features for implementing high availability within applications.

The project provides four C application programming interface (API) features:

The software is designed to operate on UDP/IP and InfiniBand networks.

Architecture

The software is composed of an executive binary which uses a client-server communication model between libraries and service engines. Loadable modules, called service engines, are loaded into the Corosync Cluster Engine and use the services provided by the Corosync Service Engine internal API.

The services provided by the Corosync Service Engine internal API are:

Additionally Corosync provides several default service engines that are used via C APIs:

History

The project was formally announced in July 2008 via a conference paper at the Ottawa Linux Symposium. [5] The source code of OpenAIS was refactored such that the core infrastructure components were placed into Corosync and the SA Forum APIs were kept in OpenAIS.

In the second version of corosync, published in 2012, quorum subsystem was changed and integrated into the daemon. [6] This version is available since Fedora 17 and RHEL7. [7]

Flatiron branch (1.4.x) development ended with 1.4.10 release. [8] Needle branch was announced stable with 2.0.0 release on 10 April 2012. [9] [10] Development of this branch stopped with 2.4.6 release on 9 November 2022, because 3.x branch (Camelback) was considered to be stable after almost 4 years of work. [9]

See also

References

  1. ↑ "Release 3.1.9". 15 November 2024. Retrieved 22 November 2024.
  2. ↑ Amir, Y.; Moser, L.E.; Melliar-Smith, P.M.; Agarwal, D.A.; Ciarfella, P. (November 1995). "The Totem Single Ring Ordering and Membership Protocol". ACM Transactions on Computer Systems. 13 (4): 311–342. doi:10.1145/210223.210224. S2CID   15165593.
  3. ↑ Moser, L.E.; Amir, Y.; Melliar-Smith, P.M.; Agarwal, D.A. (November 1995). "Extended Virtual Synchrony". ACM Transactions on Computer Systems. 13 (4): 311–342. doi:10.1145/210223.210224. S2CID   15165593. Also in Proceedings of DCS, pp. 56-65, 1994.
  4. ↑ Dake, S. (July 2009). "The Corosync High Performance Shared Memory IPC Reusable C Library" (PDF). Proceedings of the Linux Symposium: 61–68.
  5. ↑ Dake, S.; Caulfield, C.; Beekhof, A. (July 2008). "The Corosync Cluster Engine" (PDF). Proceedings of the Linux Symposium: 85–99.
  6. ↑ Christine Caulfield,New quorum features in Corosync 2 - 2012-2016 (in English)
  7. ↑ Linux Cluster next generation, LVEE, 2013
  8. ↑ "Releases v1.4.10". GitHub . Retrieved 23 November 2022.
  9. 1 2 "Releases v2.4.6". GitHub . Retrieved 23 November 2022.
  10. ↑ "Releases v2.0.0". GitHub . Retrieved 23 November 2022.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.