BOOTSTRAP(5) File Formats Manual BOOTSTRAP(5) NAME bootstrap - Univa Grid Engine bootstrap file DESCRIPTION bootstrap contains parameters that are needed for the startup of Univa Grid Engine components. It is created during the sge_qmaster installa- tion. Modifying bootstrap in a running system is not supported. FORMAT The paragraphs that follow provide brief descriptions of the individual parameters that compose the bootstrap configuration for a Univa Grid Engine cluster: admin_user Administrative user account used by Univa Grid Engine for all internal file handling (status spooling, message logging, etc.). Can be used in cases where the root account does not have the corresponding file access permissions (e.g. on a shared file system without global root read/write access). Being a parameter set at installation time changing admin_user in a running system is not supported. Changing it manually on a shut-down cluster is possible, but if access to the Univa Grid Engine spooling area is interrupted, this will result in unpredictable behavior. The admin_user parameter has no default value, but instead it is defined during the master installation procedure. default_domain Only needed if your Univa Grid Engine cluster covers hosts belonging to more than a single DNS domain. In this case it can be used if your hostname resolving yields both qualified and unqualified hostnames for the hosts in one of the DNS domains. The value of default_domain is appended to the unqualified hostname to define a fully qualified host- name. The default_domain parameter will have no effect if ignore_fqdn is set to "true". Being a parameter set at installation time changing default_domain in a running system is not supported. The default for default_domain is "none", in which case it will not be used. ignore_fqdn Ignore fully qualified domain name component of hostnames. Should be set if all hosts belonging to a Univa Grid Engine cluster are part of a single DNS domain. It is switched on if set to either "true" or "1". Switching it on may solve problems with load reports due to different hostname resolutions across the cluster. Being a parameter set at installation time changing ignore_fqdn in a running system is not supported. The default for ignore_fqdn is "true". spooling_method Defines how sge_qmaster(8) writes its configuration and the status information of a running cluster. The available spooling methods are berkeleydb, postgres and classic. spooling_lib The name of a shared library containing the spooling_method to be loaded at sge_qmaster(8) initialization time. The extension character- izing a shared library (.so, .sl, .dylib etc.) is not contained in spooling_lib. If spooling_method was set to berkeleydb during installation, spool- ing_lib is set to libspoolb, if postgres was chosen as spooling_method, spooling_lib is set to libspoolp, if classic was chosen as spool- ing_method, spooling_lib is set to libspoolc. Not all operating systems allow the dynamic loading of libraries. On these platforms a certain spooling method (default: berkeleydb) is com- piled into the binaries and the parameter spooling_lib will be ignored. spooling_params Defines parameters to the chosen spooling method. Parameters that are needed to initialize the spooling framework, e.g. to open database files or to connect to a certain database server. The spooling parameters value for spooling method berkeleydb is the path to the database directory, e.g. /sge_local/default/spool/qmas- ter/spooldb for spooling to a local filesystem. For spooling method postgres the spooling parameters contain the Post- greSQL connection string in Keyword/Value format documented at http://www.postgresql.org/docs/9.3/interactive/libpq-con- nect.html#LIBPQ-CONNSTRING. For spooling method classic the spooling parameters take the form ;, e.g. /sge/default/com- mon;/sge/default/spool/qmaster binary_path The directory path where the Univa Grid Engine binaries reside. It is used within Univa Grid Engine components to locate and startup other Univa Grid Engine programs. The path name given here is searched for binaries as well as any direc- tory below with a directory name equal to the current operating system architecture. Therefore, /usr/SGE/bin will work for all architectures, if the corresponding binaries are located in subdirectories named aix43, lx-amd64, lx-x86, hp11, hp11-64, sol-amd64, sol-sparc etc. The default location for the binary path is /bin qmaster_spool_dir The location where the master spool directory resides. Only the sge_qmaster(8) and sge_shadowd(8) need to have access to this direc- tory. The master spool directory - in particular the job_scripts directory and the messages log file - may become quite large depending on the size of the cluster and the number of jobs. Be sure to allocate enough disk space and regularly clean off the log files, e.g. via a cron(8) job. Being a parameter set at installation time changing qmaster_spool_dir in a running system is not supported. The default location for the master spool directory is //spool/qmaster. security_mode The security mode defines the set of security features the installed cluster is using. Possible security mode settings are none, afs, dce, kerberos, csp. (no additional security, AFS, DCE, KERBEROS, CSP security model). listener_threads The default for this parameter will be set to 2 during installation process. Listener threads are threads that do preliminary work for worker and reader threads running in sge_qmaster(8). At least two of them are required in a system. worker_threads The default for this parameter will be set to 4 during installation process. Defines the number of worker threads that are started during sge_qmas- ter(8) start. It is not possible to disable the worker thread pool and the number of threads part of that pool cannot be adjusted dynamically. The change of this parameter requires a restart of sge_qmaster(8). The recommended value for this parameter is 4. If no server JSV is con- figured then it is possible to reduce the value to 2 without perfor- mance loss. Starting more than 4 threads will not improve sge_qmas- ter(8) scheduling and execution performance. In rare cases more than 4 threads might improve the cluster submit rate if a server JSV is con- figured that needs much time to verify one job. reader_threads The default for this parameter will be set during installation process. The value 0 means that the reader thread pool is completely disabled in the sge_qmaster(8) process. If the reader thread pool is disabled then all read-only and read-write requests will be handled by the worker threads. Values between 1 and 64 will enable the reader thread pool. The corre- sponding number of reader threads will be part of the initially created read-only thread pool when sge_qmaster(8) is started. This thread pool will then handle incoming read-only requests whereas worker threads will then handle read-write requests only. During runtime it is not possible to enable/disable the reader thread pool. To do so it is required to adjust the bootstrap parameter and to restart sge_qmaster(8). In systems where the reader thread pool is enabled it is possible to dynamically adjust the number of reader threads. The qconf(1) -at/-kt switches can be used to start/stop reader threads but any attempt to terminate the last 2 reader threads will be rejected as well as the attempt to start more that 64 threads. scheduler_threads The number of scheduler threads (allowed: 0-1, default set by installa- tion: 1, off: 0). (see qconf(1) -kt/-at option) jvm_threads The number of JVM threads (allowed: 0-1, default set by installation, off: 0). COPYRIGHT See sge_intro(1) for a full statement of rights and permissions. Univa Grid Engine File Formats UGE 8.5.4 BOOTSTRAP(5)