Jeas: Java Enhanced Availability Server - Summary
This group is not part of the GNU Project.
Jeas is a distributed, fault-tolerant system that adapts on any tcp/udp server, like web or ftp servers.
Written in Java and massively using RMI APIs.
There are a module for each real servers, a traffic manager and a data server that have to be mounted by NFS on real servers.
It work with (minimum) 3 nodes:
-the load balancer.
-one real server.
-the data serverp.
but a backup for the balancer and at least 2 or 3 reals servers are recommanded.
Features:
*- "less loaded" Load Balacing
*- High Availability
*- Reliability
*- Serviceability
*- Scalability
Here is the topomogy:
http://fixs.tuxfamily.org/projets/jeas/topo/topo_jeas.png
Modules on Reals Servers get criticals load informations from the local server : free memory, cpu charge, ...
The Traffic Manager redirect request on Real Servers depending of their current load.
The service on Real Servers (Apache, Tomcat, PureFTPD, ...) handle the request and send a response.It has a local copy of datas (that are stored on the Data Server) using NFS.
The Traffic Manager get that response and send it to the client.
It acts like a pipe.
The Traffic Manager can have Backup that is an exact clone of it.
An hearthbeat system permits to detect the primary server crash ; if it happens the backup server transparently substitute to the primary server by using ARP Poisoning (also knew as ARP Spoofing, or Gratuitous ARP).
When the primary server come back to life, the backup server detects it and stops to send ARP Echo Replies.
Registration Date: Wed 11 Sep 2002 05:29:40 PM UTC
License: GNU General Public License v2 or later
Development Status: 4 - Beta


- Browse open items
Submit a new item
Powered by Savane 3.15-e6e5.
Corresponding source code