...
- How can you tell which job is associated with an email given the email message doesn't include a working dir or the assigned batch_name?
- Is there a config option that will cause condor to not start? We have diskless nodes and it is easier to modify the config file then change systemd.
- SOLUTION: Either set START_MASTER = False or START_DAEMONS = False depending on desired outcome.
- Torque has this command called pbsnodes that can not only offline/drain a node but keeps a note about it that all can see in one place. I know I can use condor_off to drain a node but is there a central place keep notes so I can remember a month later why I set a certain node to drain?
- ANSWER: there is no place to keep such notes.
- May want to use condor_drain instead of condor_off. condor_off will kill the startd when all jobs finish and it no longer shows up in condor_status. condor_drain will leave the node in condor_status.
...
- Perhaps use requirements. Greg will send an example
- SOLUTION:
- DAG:
- JOB step05 step05.htc
- #VARS step05 SITE="chtc"
- #VARS step05 SITE="aws"
- Submit:
- +NRAOAttr = "$(SITE)"
- Requirements = My.NRAOAttr == "chtc" ? PoolName == "CHTC" : PoolName =!= "CHTC"
Requirements = My.NRAOAttr == "chtc" ? (Target.HasCHTCStaging == true) : (Target.HasCHTCStaging =!= true)
- myannex = "krowe-annex"
- +MayUseAWS = True
Requirements = My.NRAOAttr == "aws" ? AnnexName == $(myannex) : AnnexName =!= $(myannex)
- I would set myannex in the DAG but when I do that it tries to find an AnnexName of "krowe - annex" (note spaces)
- ANSWER: My conclusion is that there are limitations on what one can do with variables in the submit file that were defined in the DAG file.
- Is there a config option that will cause condor to not start? We have diskless nodes and it is easier to modify the config file then change systemd.
- SOLUTION: Either set START_MASTER = False or START_DAEMONS = False depending on desired outcome.