Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Job Rescheduling: Setting the job status and perform the rescheduling operation in a single command #7437

Closed
aldbr opened this issue Feb 2, 2024 · 2 comments
Assignees
Milestone

Comments

@aldbr
Copy link
Contributor

aldbr commented Feb 2, 2024

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.

self.jobReport.setJobStatus(status=JobStatus.RESCHEDULED, applicationStatus=message, sendFlag=True)
self.jobReport.setJob(originalJobID)
self.log.info("Job will be rescheduled")
result = JobManagerClient().rescheduleJob(jobID)

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?

@aldbr aldbr added this to the v9.0 milestone Feb 2, 2024
@aldbr aldbr self-assigned this Feb 2, 2024
@fstagni
Copy link
Contributor

fstagni commented Feb 5, 2024

I don't see any issue with that, just it would need to target v9.

@aldbr
Copy link
Contributor Author

aldbr commented Dec 2, 2024

As it is a "virtual" status that does nothing, I close the issue.

@aldbr aldbr closed this as completed Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants