Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Tools/Manuals/TS126

From EGIWiki
< Tools
Revision as of 12:39, 23 November 2012 by Krakow (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators



Back to Administration FAQ


How to drain a CE

To indicate to clients that a CE is being drained (i.e. new jobs must not be sent to that CE) at least the information system should be updated.

Well-behaved clients will consult the BDII to discover if a particular CE is ready for new jobs. The relevant attribute is GlueCEStateStatus, which can take any of the following official values per queue:

  1. Production: the queue accepts jobs and is served by the scheduler. Jobs should be sent only when the queue is in this state.
  2. Draining: the queue does not accept jobs, but is served by the scheduler. This is the state to be advertised for all queues served by the CE when the CE needs to be drained.
  3. Queueing: the queue accepts new jobs, but is not served by the scheduler.
  4. Closed: the queue does not accept jobs and is not served by the scheduler.

For a CREAM CE actual job submissions can be prevented with the glite-ce-disable-submission command, but one should still ensure the information system shows that the CE is being drained, to avoid that jobs are sent to the CE only to fail immediately.

Solution

For PBS/Torque systems the info provider will automatically determine the correct value for GlueCEStateStatus per queue based on whether the queue has been enabled and whether it has been started. If you have a single CE or you want to drain all your CEs, you can adjust the values like this:

# qmgr -c "set queue myqueue enabled=<True|False>"
# qmgr -c "set queue myqueue started=<True|False>"

If you have multiple CEs in front of the same batch system and you want to drain only some of the CEs, on those CEs you can edit the glite-info-dynamic-ce plugin like this (lines wrapped for readability):

#!/bin/sh

/opt/lcg/libexec/lcg-info-dynamic-pbs \
    /opt/glite/etc/gip/ldif/static-file-CE.ldif <your-CE> |
    sed -e 's/GlueCEStateStatus: Production/GlueCEStateStatus: Draining/'

The latter method works for any batch system.