Difference: DistributedWMS (19 vs. 20)

Revision 202009-11-10 - FabioCapannini

Line: 1 to 1
 
META TOPICPARENT name="WMS_guide"
Line: 20 to 20
 
glite-lb-bkserverd Yes / Done No

Filesystem sharing

Changed:
<
<
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.
>
>
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 choice 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: 88 to 88
  Each component stores its logs locally, this is especially important for gundam where the LM, JC and CondorG logs produce a huge amount of data.
Changed:
<
<

configuration:

  1. Set LBproxy = false in the Common section of the WMS configuration file.
  2. The log_monitor daemon looks for X509 credentials in order to authenticate with LB logd under ~glite/.globus. On gundam create the following links to avoid authentication errors (as an alternative, a valid proxy for the user "glite" can be put in /tmp/x509up_uXYZ):
>
>

Configuration

  • Set LBproxy = false in the Common section of the WMS configuration file.
  • The log_monitor daemon looks for X509 credentials in order to authenticate with LB logd under ~glite/.globus. On gundam create the following links to avoid authentication errors (as an alternative, a valid proxy for the user "glite" can be put in /tmp/x509up_uXYZ):
 
# ln -s /home/glite/.certs /home/glite/.globus
# ln -s /home/glite/.certs/hostcert.pem  /home/glite/.certs/usercert.pem
# ln -s /home/glite/.certs/hostkey.pem  /home/glite/.certs/userkey.pem
Changed:
<
<
Useful Condor tweaks:
>
>
  • Disable glite-wms-check-daemons.cron or modify /opt/glite/libexec/glite-wms-check-daemons.sh so that only the desired services are restarted
  • Useful Condor tweaks:
 SUBMIT_SEND_RESCHEDULE = False /* on high load it can happen to hit the error "Can't send RESCHEDULE command to condor scheduler" */ GRIDMANAGER_MAX_JOBMANAGERS_PER_RESOURCE = 100
Added:
>
>
 
Changed:
<
<

scripts

>
>

Scripts

  devel20:
Line: 119 to 121
 # /opt/glite/etc/init.d/glite-lb-bkserverd start/stop/status
Changed:
<
<
Gundam must be superuser for the LB@devel20
>
>

 A preview from stress tests recently made with CMS (thanks to Enzo Miccio): a >1Hz stable rate to Condor (blue line) whenever Grid resources were able to keep the pace: These test have been made with an experimental version for the gLite WMS which will be released after patch #1841. -- FabioCapannini - 02 Oct 2008 \ No newline at end of file
 
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