Changes between Version 16 and Version 17 of LoadBalanceable

Timestamp:

Sep 21, 2012, 5:51:41 AM (12 years ago)

Author:

heikki

Comment:

--

LoadBalanceable

@@ -2 +2 @@
 
 || '''Date''' || 2012/03/22 ||
-|| '''Contact(s)''' || Heikki Doeleman, Jose García||
+|| '''Contact(s)''' || Heikki Doeleman, Jose García, Steven Smolders||
 || '''Last edited''' || ||
 || '''Status''' || Proposed for vote||
 || '''Assigned to release''' || 2.9 ||
-|| '''Resources''' || Available ||
+|| '''Resources''' || from AGIV http://www.agiv.be ||
 || '''Ticket #''' || #432 ||
 
@@ -30 +30 @@
 
  * Various users of GeoNetwork would like to be able to scale it horizontally to provide for increased performance and fail-over.
+
+== Example ==
+
+The diagram below illustrates a possible cluster configuration. The cluster consists of 3 redundant GeoNetwork instances. The instances share the database, the shared data directory, and the JMS server ([http://activemq.apache.org/ ActiveMQ]). A loadbalancer hides the actual, different URLs to these GeoNetwork instances so this clustered catalogue is accessed by users through a single URL. The users do not know which GeoNetwork node serves them, nor that this catalog is horizontally scaled at all.
+
+[[Image(cluster.png)]]
+
+You notice that each of the GeoNetwork nodes maintains its own Lucene index and (if configured) SVN repo. This does not impair functionality as the indexes and the SVN repos are kept in sync. However it might be better to use a shared Lucene index, at least. Future work may explore how to do that, possibly using [http://lucene.apache.org/solr/ SOLR].
+
+Note that the database and the JMS server could be horizontally scaled as well, but that's outside the scope of this proposal.
+
 
 == Proposal ==