Changes between Version 6 and Version 7 of LoadBalanceable
- Timestamp:
- Mar 22, 2012, 1:45:48 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LoadBalanceable
v6 v7 29 29 == Motivations == 30 30 31 * Various users of GeoNetwork would like to be able to scale it horizontally to provide for increased performance .31 * Various users of GeoNetwork would like to be able to scale it horizontally to provide for increased performance and fail-over. 32 32 33 33 == Proposal == 34 This proposal assumes an infrastructure where multiple GeoNetwork nodes act as a single catalog. The nodes will share one database (this may be scaled separately but is not in scope of this proposal). Each node maintains its own local Lucene index and, if configured, SVN. This proposal does not address making GeoNetwork's HTTPSession serializable; therefore load-balancing using sticky sessions is presumed, and there is no support for transparentfail-over.34 This proposal assumes an infrastructure where multiple GeoNetwork nodes act as a single catalog. The nodes will share one database (this may be scaled separately but is not in scope of this proposal). Each node maintains its own local Lucene index and, if configured, SVN. This proposal does not address making GeoNetwork's HTTPSession serializable; therefore load-balancing using sticky sessions is presumed, and there is no support for ''transparent'' fail-over. 35 35 36 36 === database primary key values ===