table of contents
other versions
- wheezy 6.2u5-7.1
- jessie-backports 8.1.9+dfsg-1~bpo8+1
- testing 8.1.9+dfsg-4
- unstable 8.1.9+dfsg-4
COMPLEX(5) | Sun Grid Engine File Formats | COMPLEX(5) |
NAME¶
complex - Sun Grid Engine complexes configuration file formatDESCRIPTION¶
Complex reflects the format of the Sun Grid Engine complex configuration. The definition of complex attributes provides all pertinent information concerning the resource attributes a user may request for a Sun Grid Engine job via the -l option and for the interpretation of these parameters within the Sun Grid Engine system. The Sun Grid Engine complex object defines all entries which are used for configuring the global, the host, and queue object. The system has a set of pre defined entries, which are assigned to a host or queue per default. In a addition can the user define new entries and assign them to one or multiple objects. Each load value has to have its corresponding complex entry object, which defines the type and the relational operator for it.defining resource attributes¶
The complex configuration should not be accessed directly. In order to add or modify complex entries, the options -Mc and -mc should be used instead. While the -Mc option takes a complex configuration file as an argument and overrides the current configuration, the -mc option bring up an editor filled in with the current complex configuration.working with resource attributes¶
Before a user can request a resource attribute it has to be attached to the global, host, or cqueue object. The resource attribute exists only for the objects, it got attached to ( if it is attached to the global object(qconf -me global), it exits system wide, host object: only on that host (qconf -me NAME): cqueue object: only on that cqueue (qconf -mq NAME)).Default queue resource attributes¶
In its default form it contains a selection of parameters in the queue configuration as defined in The queue configuration parameters being requestable for a job by the user in principal are:qname hostname notify calendar min_cpu_interval tmpdir seq_no s_rt h_rt s_cpu h_cpu s_data h_data s_stack h_stack s_core h_core s_rss h_rss
Default host resource attributes¶
The standard set of host related attributes consists of two categories. he first category is built by several queue configuration attributes which are particularly suitable to be managed on a host basis. These attributes are:slots s_vmem h_vmem s_fsize h_fsize
(please refer to for details).
Overriding attributes¶
One attribute can be assigned to the global object, host object, and queue object at the same time. On the host level it might get its value from the user defined resource limit and a load sensor. In case that the attribute is a consumable, we have in addition to the resource limit and its load report on host level also the internal usage, which the system keeps track of. The merge is done as follows:- global by hosts and queues
- hosts by queues and load values or resource limits on the same level.
FORMAT¶
The principal format of a complex configuration is that of a tabulated list. Each line starting with a '#' character is a comment line. Each line despite comment lines define one element of the complex. A element definition line consists of the following 8 column entries per line (in the order of appearance):name¶
The name of the complex element to be used to request this attribute for a job in the -l option. A complex attribute name (see complex_name in may appear only once across all complexes, i.e. the complex attribute definition is unique.shortcut¶
A shortcut for name which may also be used to request this attribute for a job in the -l option. An attribute shortcut may appear only once across all complexes, so as to avoid the possibility of ambiguous complex attribute references.type¶
This setting determines how the corresponding values are to be treated Sun Grid Engine internally in case of comparisons or in case of load scaling for the load complex entries:- •
- With INT only raw integers are allowed.
- •
- With DOUBLE floating point numbers in double precision (decimal and scientific notation) can be specified.
- •
- With TIME time specifiers are allowed. Refer to for a format description.
- •
- With MEMORY memory size specifiers are allowed. Refer to for a format description.
- •
- With BOOL the strings TRUE and FALSE are allowed. When used in a load formula (refer to ) TRUE and FALSE get mapped into '1' and '0'.
- •
- With STRING all strings are allowed and is used for
wildcard regular boolean expression matching. Please see manpage for
expression definition.
Examples: -l arch="*x24*|sol*" : results in "arch=lx24-x86" OR "arch=lx24-amd64" OR "arch=sol-sparc" OR "arch=sol-sparc64" OR "arch=sol-x86" OR ... -l arch="sol-x??" : results in "arch=sol-x86" OR "arch=sol-x64" OR ... -l arch="lx2[246]-x86" : results in "arch=lx22-x86" OR "arch=lx24-x86" OR "arch=lx26-x86" -l arch="lx2[4-6]-x86" : results in "arch=lx24-x86" OR "arch=lx25-x86" OR "arch=lx26-x86" -l arch="lx2[24-6]-x86" : results in "arch=lx22-x86" OR "arch=lx24-x86" OR "arch=lx25-x86" OR "arch=lx26-x86" -l arch="!lx24-x86&!sol-sparc" : results in NEITHER "arch=lx24-x86" NOR "arch=sol-sparc" -l arch="lx2[4|6]-x86" : results in "arch=lx2[4" OR "arch=6"
- •
- CSTRING is like STRING except comparisons are case insensitive.
- •
- RESTRING is like STRING and it will be deprecated in the future.
- •
- HOST is like CSTRING but the expression must match a valid hostname.
relop¶
The relation operator. The relation operator is used when the value requested by the user for this parameter is compared against the corresponding value configured for the considered queues. If the result of the comparison is false, the job cannot run in this queue. Possible relation operators are "==", "<", ">", "<=", ">=" and "EXCL". The only valid operator for string type attributes is "==".requestable¶
The entry can be used in a resource request if this field is set to 'y' or 'yes'. If set to 'n' or 'no' this entry cannot be used by a user in order to request a queue or a class of queues. If the entry is set to 'forced' or 'f' the attribute has to be requested by a job or it is rejected.consumable¶
The consumable parameter can be set to either 'yes' ('y' abbreviated), 'no' ('n') or 'JOB' ('j'). It can be set to 'yes' and 'JOB' only for numeric attributes (INT, DOUBLE, MEMORY, TIME - see type above). If set to 'yes' or 'JOB' the consumption of the corresponding resource can be managed by Sun Grid Engine internal bookkeeping. In this case Sun Grid Engine accounts for the consumption of this resource for all running jobs and ensures that jobs are only dispatched if the Sun Grid Engine internal bookkeeping indicates enough available consumable resources. Consumables are an efficient means to manage limited resources such a available memory, free space on a file system, network bandwidth or floating software licenses.default¶
Meaningful only for consumable complex attributes (see consumable parameter above). Sun Grid Engine assumes the resource amount denoted in the default parameter implicitly to be consumed by jobs being dispatched to a host or queue managing the consumable attribute. Jobs explicitly requesting the attribute via the -l option to override this default value.urgency¶
The urgency value allows influencing job priorities on a per resource base. The urgency value effects the addend for each resource when determining the resource request related urgency contribution. For numeric type resource requests the addend is the product of the urgency value, the jobs assumed slot allocation and the per slot request as specified via -l option to For string type requests the resources urgency value is directly used as addend. Urgency values are of type real. See under for an overview on job priorities.SEE ALSO¶
Sun Grid Engine Installation and Administration Guide.COPYRIGHT¶
See for a full statement of rights and permissions.$Date$ | SGE 6.2u5 |