Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Gyrex/Development Space/ZooKeeper Interaction
< Gyrex | Development Space
Revision as of 15:05, 13 October 2011 by Gunnar.wagenknecht.org (Talk | contribs)
| Gyrex | |
| Website | |
| Download | |
| Community | |
| Mailing List • Forums • IRC • mattermost | |
| Issues | |
| Open • Help Wanted • Bug Day | |
| Contribute | |
| Browse Source • Project Set File |
This article provides insights into how Gyrex interacts with ZooKeeper.
Prerequisites
Please read about ZooKeeper. This article may use terminology which is specific to ZooKeeper and also goes right into the details.
Summary
ZooKeeper is used in Gyrex in order to implement the core functionality of clustering in Gyrex:
- Which node belongs to the cloud? (Membership)
- Which node offers which functionality in the cloud? (Coordination)
ZooKeeper also offers receipts which allow to implement additional functionality. Based on those receipts the following additional capabilities are also implemented in Gyrex:
- Eclipse Preferences
cloudScope which stores preferences in ZooKeeper - Queue Service (similar to Amazon SQS) which allows to post and receive messages with a visibility timout
- Lock Service which allows to create distributed locks (based on ephemeral as well as persistent nodes)