Project

General

Profile

Bug #23339

Make wholenode knobs uniform

Added by Marco Mascheroni over 1 year ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
Marco Mascheroni
Category:
-
Target version:
v3_7_3
Start date:
09/26/2019
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:

Factory Ops

Duration:

Description

Right now the way to set up a whole node entry is the following:

           <attr name="GLIDEIN_CPUS" const="True" glidein_publish="False" job_publish="True" parameter="True" publish="True" type="string" value="auto"/>
            <attr name="GLIDEIN_ESTIMATED_CPUS" const="True" glidein_publish="False" job_publish="True" parameter="True" publish="True" type="string" value="8"/>
            <attr name="GLIDEIN_MaxMemMBs" const="True" glidein_publish="True" job_publish="False" parameter="True" publish="True" type="string" value=""/>
            <attr name="GLIDEIN_MaxMemMBs_Estimate" const="True" glidein_publish="True" job_publish="False" parameter="True" publish="True" type="string" value="True"/>

In particular, if GLIDEIN_MaxMemMBs is set it takes the precedence over the estimation and we use that value. So, in the production factory it has to be set to an empty string because the attribute has a global default value of 2500.
Also, the GLIDEIN_MaxMemMBs/GLIDEIN_MaxMemMBs_Estimate has a different semantics compared to GLIDEIN_CPUS/GLIDEIN_ESTIMATED_CPUS.

I susggest to we use GLIDEIN_MaxMemMBs=auto to enable the estimation, and then use GLIDEIN_MaxMemMBs_Estimate in order to provide an estimation of the memory for the frontend matchmaking (which we will need to implement!).

Related issues

Related to GlideinWMS - Feature #25076: Add knobs to control the Disk amount and Memory amount at the slot level in the GlideinsClosed10/14/2020

History

#1 Updated by Marco Mascheroni over 1 year ago

  • Stakeholders updated (diff)

#2 Updated by Marco Mambelli 11 months ago

  • Target version changed from v3_7 to v3_7_1

#3 Updated by Marco Mambelli 3 months ago

GLIDEIN_MaxMemMBs and GLIDEIN_MaxMemMBs_Estimate are used in glidein_memory_setup.sh and at the end set the MEMORY attribute in the condor configuration.

add_config_line MEMORY "${GLIDEIN_MaxMemMBs}" 
add_condor_vars_line MEMORY "C" "-" "+" "N" "N" "-"

From the condor manual, https://htcondor.readthedocs.io/en/latest/admin-manual/configuration-macros.html#MEMORY :
MEMORY
Normally, HTCondor will automatically detect the amount of physical memory available on your machine. Define MEMORY to tell HTCondor how much physical memory (in MB) your machine has, overriding the value HTCondor computes automatically. The actual amount of memory detected by HTCondor is always available in the pre-defined configuration macro DETECTED_MEMORY .

RESERVED_MEMORY
How much memory would you like reserved from HTCondor? By default, HTCondor considers all the physical memory of your machine as available to be used by HTCondor jobs. If RESERVED_MEMORY is defined, HTCondor subtracts it from the amount of memory it advertises as available.

#4 Updated by Marco Mambelli 3 months ago

  • Related to Feature #25076: Add knobs to control the Disk amount and Memory amount at the slot level in the Glideins added

#5 Updated by Dennis Box 3 months ago

  • Target version changed from v3_7_1 to v3_7_2

#6 Updated by Marco Mascheroni about 2 months ago

  • Target version changed from v3_7_2 to v3_7_3

Also available in: Atom PDF