38 0x26 nid00038 24 515758 busy
39 0x27 nid00039 24 515758 idle
40 0x28 nid00040 24 515758 idle
41 0x29 nid00041 24 515758 idle
42 0x2a nid00042 24 515758 busy
43 0x2b nid00043 24 515758 busy
44 0x2c nid00044 24 515758 idle
45 0x2d nid00045 24 515758 idle
Node names that are marked as
unavail
are hidden from Mesos as available compute
resources, such as the login node (
nid00030
). In the example above, some nodes have 24
CPUs/node, some have 32 CPUs/node and some have 36 CPUs/node. While not a typical
situation,
mrun
does support this configuration, and a command such as
mrun
-n
144 -N
4 ....
would in fact be allowed to proceed, and would be limited to using 4 nodes on
nid000[16-29]
, as they are the only ones with
(144/4 = 36)
CPUs per node.
Configuration Files
When
mrun
is invoked, it sets up some internal default values for required settings.
mrun
will then check if any
system defaults have been configured in the
/etc/mrun/mrun.conf
file. An example
mrun.conf
file is shown
below:
#
# (c) Copyright 2016 Cray Inc. All Rights Reserved.
#
# Anything after an initial hashtag '#' is ignored
# Blank lines are ignored.
#
#NCMDServer=nid00000
#MesosServer=localhost # same as --host
#MesosPort=5050
#MarathonServer=localhost
#MarathonPort=8080
#DebugFLAG=False # same as --debug
#VerboseFLAG=False # same as --verbose
#JobTimeout=0-0:10:0 # ten minutes, same as --time
#StartupTimeout=30 # 30 seconds, same as --immediate
#HealthCheckEnabled=True # Run with Marathon Health Checks enabled
#HCGracePeriodSeconds=5 # Seconds at startup to delay Health Checks
#HCIntervalSeconds=10 # Seconds between Health Check pings
#HCTimeoutSeconds=10 # Seconds to answer Health Check successfully
#HCMaxConsecutiveFailures=3 # How many missed health checks before app killed
If any of the lines above are not commented out, those values will become the new defaults for every
mrun
invocation.
Additionally, after the system
/etc/mrun/mrun.conf
file is loaded (if it exists), the user's private
$HOME/.mrun.conf
file will be loaded (if it exists). The following items should be noted:
●
Any settings in the user's
$HOME/.mrun.conf
file will take precedence over any conflicting settings in the
system
/etc/mrun/mrun.conf
file.
●
Any command-line arguments that conflict with any pre-loaded configuration file settings will take precedence
for the current invocation of
mrun
.
For more information, see the
mrun(1)
man page.
Resource Management
S3016
132
