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
Currently, there is a distinct separation in our workflow between marking a job as RESCHEDULED and performing the rescheduling action itself. This means if one process encounters an error, the other can still proceed without issue. This separation introduces complexity and potential points of failure.
We could streamline this process by integrating the status update directly within the JobManager. This integration would necessitate adding a 'reason' parameter to the interface to accommodate detailed reporting on why a job was rescheduled. This would not only simplify the workflow but also provide a clearer, more concise handling of job statuses.
This change would require modifications to the interface, both in DIRAC and diracx.
Any thought?
The text was updated successfully, but these errors were encountered:
Currently, there is a distinct separation in our workflow between marking a job as
RESCHEDULED
and performing the rescheduling action itself. This means if one process encounters an error, the other can still proceed without issue. This separation introduces complexity and potential points of failure.DIRAC/src/DIRAC/WorkloadManagementSystem/Agent/JobAgent.py
Lines 833 to 837 in 80ea404
We could streamline this process by integrating the status update directly within the
JobManager
. This integration would necessitate adding a 'reason' parameter to the interface to accommodate detailed reporting on why a job was rescheduled. This would not only simplify the workflow but also provide a clearer, more concise handling of job statuses.This change would require modifications to the interface, both in DIRAC and diracx.
Any thought?
The text was updated successfully, but these errors were encountered: