karaf-cellar | Mirror of Apache Karaf Cellar | Telnet library
kandi X-RAY | karaf-cellar Summary
kandi X-RAY | karaf-cellar Summary
Apache Karaf Cellar is an Apache Karaf subproject. It provides a clustering solution for Apache Karaf powered by Hazelcast. Cellar allows you to manage a cluster of several Karaf instances, provinding synchronization between instances. Here is a short list of features: * Discovery: when you install Cellar into a Karaf instance, it automatically tries to discover other Cellar instances and join the cluster. There is no configuration required to join the cluster, the discovery is made behind the scene. You can use multicast or unicast for discovery. * Cluster group: a Karaf node could be part of one or more cluster group. In Cellar, you can define cluster group depending of your requirements. The resources will be sync between nodes of the same group. * Distributed Configuration Admin: Cellar distributes the configuration data. The distribution is event driven and filtered by group. You can tune the configuration replication using blacklist/whitelist on the configuration ID (PID). * Distributed Features Service: Cellar distributes the features/repositories info. It’s also event-driven. * Provisioning: Cellar provides shell commands for basic provisioning. It can also use an OBR backend or another provisioning tool such as Apache ACE.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Start the discovery service
- Start the repository
- Initialize the Etcd
- Starts the bundle
- Starts the cluster
- Initialize the configuration handler
- Starts the OCBR event handler
- Starts the balancer
- Start the remote service call handler
- Initialize cluster event handler
- Start the kar
- Starts the server
- Start the server
- Starts the event handler tracker
- Starts the GREeter process
- Start the service
- Starts the kubernetes service
- Initialize the cloud discovery service
- Cleanup resources
- Destroy this instance
- Unregister resources
- Destroys the bean
- Main execution method
- Execute the cluster
- Execute the clustering
- Handle a cluster feature event
- Executes the event producer
- Executes the update
- Called when a remote feature repository is changed
- Called when a bundle is changed
- Returns a table with all the bundles
karaf-cellar Key Features
karaf-cellar Examples and Code Snippets
Community Discussions
Trending Discussions on karaf-cellar
QUESTION
I'm looking to implement failover (master/slave) for Karaf. Our current server setup has two application servers that have a shared SAN disk where our current Java applications are installed in a single location and can be started on either machine or both machines at the same time.
I was looking to implement Karaf master/slave failover in a similar way (one install being shared by both app servers), however I'm not sure that this is really a well beaten path and would appreciate some advice on whether the alternatives (mentioned below) are significantly better.
Current idea for failover: Install Karaf once on the shared SAN and setup basic file locking on this shared disk. Both application servers will effectively initiate the Karaf start script, however only one (the first) will fully start (grabbing the lock) and the second will remain in standby until it grabs the lock (if the master falls over)
The main benefit I can see from this is that I only have to manage deploying components to one Karaf installation and I only need to manage one Karaf installation.
Alternatives: We install Karaf in two separate locations on the shared SAN and setup to lock to the same lock file. Each application server will have their own Karaf instance, thus start script to run.
This will make our deployment slightly more complicated (2 Karaf installations to manage and deploy to).
I'd be interested if anyone can indicate any specific concerns that they have with the current idea.
Note: I understand that Karaf-cellar can simplify my Karaf instance management, however we would need to undertake another round of PoCs etc.. to approve our company use of cellar (as a separate product). Something that I'd like to migrate to in the future.
...ANSWER
Answered 2017-Feb-17 at 18:52Take a look at the documentation
This is from the documentation on how to set a lockfile for HA:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install karaf-cellar
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page