You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rename ROOT type to MAIN. So that dagman jobs will have CRAB_DagType in ["MAIN", "PROCESSING", "TAIL"]. "normal" tasks will only have "MAIN". "automatic" will use "MAIN" for running probes, followed by "PROCESSING" and up to 3 "TAIL".
But I am still not happy here. ROOT is more descriptive for a DAG which can be either the full thing standalone or the probe step for automatic splitting. Maybe "BASE" ?
I will start with renaming the classAd, at least it will make it easier later on to identify where it is used and possibly change the value.
BEWARE these changes will not be backward compatible ! i.e. crab kill and crab resubmit will not work on tasks which have TaskType but not CRAB_DAGType.
add a backward-compatibility layer (to be remove after 2 months in production)
Note: ROOT is assigned in initial submission (so it i the same for everybody) in DagamSubmitter. Later on PreDag uses the stage name when it submits the various subdags. Stage name is set in DagmanCreator and used in PreDag and PreJob
List of possible values. Note that CRAB_DAGType is the classAd of a job !! Simply it takes a non trivial value when the job runs in the Scheduler universe to execut a DagMan
in the context of Modernize HTC calls
see #8337 (comment)
But I am still not happy here. ROOT is more descriptive for a DAG which can be either the full thing standalone or the probe step for automatic splitting. Maybe "BASE" ?
I will start with renaming the classAd, at least it will make it easier later on to identify where it is used and possibly change the value.
BEWARE these changes will not be backward compatible ! i.e.
crab kill
andcrab resubmit
will not work on tasks which have TaskType but not CRAB_DAGType.Note: ROOT is assigned in initial submission (so it i the same for everybody) in DagamSubmitter. Later on PreDag uses the stage name when it submits the various subdags. Stage name is set in DagmanCreator and used in PreDag and PreJob
List of possible values. Note that CRAB_DAGType is the classAd of a job !! Simply it takes a non trivial value when the job runs in the Scheduler universe to execut a DagMan
Possible alternative names for ROOT: MAIN , BASE
TaskType ad is defined in
CRABServer/src/python/TaskWorker/Actions/DagmanSubmitter.py
Line 529 in 3c826e3
and
CRABServer/src/python/TaskWorker/Actions/DagmanCreator.py
Line 104 in 43208f8
and in case of automatic splitting in
CRABServer/src/python/TaskWorker/Actions/PreDAG.py
Line 338 in 3c826e3
the
stage
in PreDAG is passed as argument when PreDAG is called during Dag execution:CRABServer/src/python/TaskWorker/Actions/DagmanCreator.py
Line 56 in 3c826e3
and the code which managed the various DAGs creation is the somehow cryptic
CRABServer/src/python/TaskWorker/Actions/DagmanCreator.py
Lines 998 to 1024 in 3c826e3
TaskType ad is also used in
CRABServer/scripts/task_process/task_proc_wrapper.sh
Lines 73 to 77 in 43208f8
CRABServer/scripts/AdjustSites.py
Line 452 in 43208f8
CRABServer/src/python/TaskWorker/Actions/DagmanResubmitter.py
Line 73 in 43208f8
CRABServer/src/python/TaskWorker/Actions/Recurring/RenewRemoteProxies.py
Line 153 in 43208f8
CRABServer/src/python/TaskWorker/Actions/DagmanKiller.py
Line 63 in 43208f8
CRABServer/src/python/TaskWorker/Actions/DagmanKiller.py
Line 75 in 43208f8
The text was updated successfully, but these errors were encountered: