Difference: DistributedWMS (16 vs. 17)

Revision 172009-11-04 - MarcoCecchi

Line: 1 to 1
 
META TOPICPARENT name="WMS_guide"

HOW-TO optimise performance distributing WMS and LB on two hosts

WMS+LB physical architecture

Changed:
<
<
In order to gain better performance, the components of a single WMS instance have been distributed on two hosts according to a layout different from the typical one. LBserver is hosted on one machine, in our case devel20, together with WMproxy and WM and without LBproxy, not to store the same events twice on database (this issue will disappear with the advent of LB 2.0) . The Job Submission Service is moved to another machine, gundamfor us. JC+LM+CondorG are hosted by gundam. They connect to the LBserver at devel20 without using an LBproxy outpost on gundam.
>
>
In order to gain better performance, the components of a single WMS instance have been distributed on two hosts according to a layout different from the typical one. LBserver is hosted on one machine, in our case devel20, together with WMproxy and WM and without LBproxy, not to store the same events twice on database (this issue will disappear with the advent of LB 2.0) . The Job Submission Service is moved to another machine, 'gundam' in our case, so that JC+LM+CondorG are hosted by gundam. They connect to the LBserver at devel20 without using an LBproxy outpost on gundam.
 
Changed:
<
<
Configure LBproxy = false on gundam.
>
>
COMPONENTS LAYOUT:
 
Components host devel20 host gundam
glite_wms_wmproxy Yes / Done No
Line: 18 to 18
 
glite-lb-logd Yes / Done Yes / Done
glite-lb-interlogd Yes / Done Yes / Done
glite-lb-bkserverd Yes / Done No
Added:
>
>
 

Filesystem sharing

Changed:
<
<
Interoperation between the various WMS components running on two different hosts is (temporarily) guaranteed by exporting /var/glite on devel20 to the host gundam via NFS, this is done only for simplicity. gundam mounts the filesystem under /mnt/devel20. Since the gahp_server is highly CPU-bound this physical architecture should be better than just using a WMS+LB on a single machine with two separately controlled disks.
>
>
Interoperation between the various WMS components running on two different hosts is guaranteed by exporting /var/glite on devel20 to the host gundam via NFS, this choise is only done for simplicity. gundam mounts devel20 filesystem under /mnt/devel20. Since the gahp_server is also CPU-bound, other than I/O bound, this physical architecture should be better than just using a WMS+LB on a single machine with two separately controlled disks.
 

devel20: NFS server configuration

On devel20, as root, insert the following lines in /etc/hosts.deny:
Line: 91 to 92
  This is more than important because ClassAds attributes will still point to the canonical "/var/glite/...."
Changed:
<
<

configuration

>
>

configuration steps:

 On devel20 no changes were made to the default configuration file glite_wms.conf.
On gundam it is necessary to update some entries for the JobController and LogMonitor to find the jobdir under /mnt/devel20.

  1. On gundam
Added:
>
>
Configure LBproxy = false in the Common section of the WMS configuration file.
  after "exporting"
       GLITE_LOCAL_LOCATION_LOG=/var/log/glite 
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback