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.
Difference between revisions of "Gyrex/Development Space/ZooKeeper Interaction"
| Line 5: | Line 5: | ||
== Prerequisites == | == Prerequisites == | ||
| − | |||
Please read about [http://zookeeper.apache.org/|Apache ZooKeeper]. This article may use terminology which is specific to ZooKeeper and also goes right into the details. | Please read about [http://zookeeper.apache.org/|Apache ZooKeeper]. This article may use terminology which is specific to ZooKeeper and also goes right into the details. | ||
== Summary == | == Summary == | ||
| − | |||
ZooKeeper is used in Gyrex in order to implement the core functionality of clustering in Gyrex: | 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 belongs to the cloud? (Membership) | ||
| Line 24: | Line 22: | ||
The ZooKeeper gate is the central point in Gyrex which coordinates all communication to ZooKeeper. It is responsible for establishing and maintaining a ZooKeeper connection. Listeners can be registered with the gate in order to participate in the connection life cycle. | The ZooKeeper gate is the central point in Gyrex which coordinates all communication to ZooKeeper. It is responsible for establishing and maintaining a ZooKeeper connection. Listeners can be registered with the gate in order to participate in the connection life cycle. | ||
| + | |||
| + | === Gate Manager === | ||
| + | The gate itself is maintained by a gate manager (ZooKeeperGateApplication). This is an Equinox IApplication which must be started in order to enable participation of the node in the cloud. The application is contributed using the an Eclipse Extension | ||
Revision as of 15:21, 13 October 2011
| 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:
- Cloud Preferences Scope 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)
ZooKeeper Gate
The ZooKeeper gate is the central point in Gyrex which coordinates all communication to ZooKeeper. It is responsible for establishing and maintaining a ZooKeeper connection. Listeners can be registered with the gate in order to participate in the connection life cycle.
Gate Manager
The gate itself is maintained by a gate manager (ZooKeeperGateApplication). This is an Equinox IApplication which must be started in order to enable participation of the node in the cloud. The application is contributed using the an Eclipse Extension