Hello Tomer,
Thanks for sharing the configuration. it helps to put the job on hold breaching the requestdisk. We have a problem in our infra where people don't ask for the request disk in job spec hence I want to modify it on a worker machine based on some logic related to CPUs. I am seeing strange behavior.
RequestDisk will remain intact whatever we put in the job submit file 2GB but I Âcouldn't understand where it's picking the Disk attribute. By default it's ~ 4GB
# condor_who -af:h globaljobid disk DiskUsage TotalDisk TotalSlotDisk RequestDisk
globaljobid                    Âdisk   DiskUsage TotalDisk ÂTotalSlotDisk     RequestDisk
test.example.com#429.0#1685829846 4271297 Â27 Â Â Â Â4271296648 4271297.0 Â Â Â Â Â Â 2097152
Attempt 1 : Try to modify the RequestDisk to 4GB but it becomes 8GB - May be addition of default 4GB
MODIFY_REQUEST_EXPR_REQUESTDISK = 4194304
globaljobid                    Âdisk   DiskUsage TotalDisk ÂTotalSlotDisk     RequestDisk
test.example.com#430.0#1685830072 8542594 Â27 Â Â Â Â4271296648 8542594.0 Â Â Â Â Â Â 2097152
Attempt 2 : Try to modify the RequestDisk to 6GB but it becomes 8GB - If we go by 4GB addition logic it should have been 10GB
MODIFY_REQUEST_EXPR_REQUESTDISK = 6291456
globaljobid                    Âdisk   DiskUsage TotalDisk ÂTotalSlotDisk     RequestDisk
test.example.com#431.0#1685830179 8542594 Â2 Â Â Â Â 4271296648 8542594.0 Â Â Â Â Â Â 2097152
Attempt 3 : Try to modify the RequestDisk to 8GB as expected it becomes 12GB.
MODIFY_REQUEST_EXPR_REQUESTDISK = 8388608
globaljobid                    Âdisk   DiskUsage TotalDisk ÂTotalSlotDisk     RequestDisk
test.example.com#428.0#1685829703 12813890 8192027 Â 4271296648 12813890.0 Â Â Â Â Â Â2097152 Â Â Â Â Â
Attempt 4 : Try to modify the disk size to 1GB. it retains 4GB size.
MODIFY_REQUEST_EXPR_REQUESTDISK = 1048576
globaljobid                    Âdisk   DiskUsage TotalDisk ÂTotalSlotDisk     RequestDisk
test.example.com#432.0#1685830887 4271297 Â2 Â Â Â Â 4271296648 4271297.0 Â Â Â Â Â Â 2097152
Command used to grab outputs:
condor_who -af:h globaljobid disk DiskUsage TotalDisk TotalSlotDisk RequestDisk
Finally more confusion with negative disk values in following output:
# condor_status `hostname` -server
Name                      OpSys    Arch  LoadAv Memory  Disk   ÂMips  ÂKFlops
slot1@xxxxxxxxxxxxxxxxxxxxxxxxxx  LINUX    X86_64 Â0.000  172962 -57841021  22492  1705677
slot1_1@xxxxxxxxxxxxxxxxxxxxxxxxxx LINUX Â Â Â X86_64 Â0.000 Â Â19218 Â12813890 Â 22492 Â 1705677
slot1_2@xxxxxxxxxxxxxxxxxxxxxxxxxx LINUX Â Â Â X86_64 Â0.000 Â Â19218 Â 8542594 Â 22492 Â 1705677
slot1_3@xxxxxxxxxxxxxxxxxxxxxxxxxx LINUX Â Â Â X86_64 Â0.000 Â Â19218 Â 8542594 Â 22492 Â 1705677
slot1_4@xxxxxxxxxxxxxxxxxxxxxxxxxx LINUX Â Â Â X86_64 Â0.000 Â Â19218 Â 4271297 Â 22492 Â 1705677
       ÂMachines Avail ÂMemory    ÂDisk    ÂMIPS   ÂKFLOPS
 X86_64/LINUX    Â5   5   Â249834 18446744073685880970   Â112460   8528385
    ÂTotal    Â5   5   Â249834 18446744073685880970   Â112460   8528385
Questions:
- From where it's picking the default 4GB Disk size?
- Why is it setting Disk size to different values than what we ask in the modify _expression_?
- Why in -server output we see negative disk value.
htcondor version : 9.0.17