-
Notifications
You must be signed in to change notification settings - Fork 31
Refactor Job manager routes #296
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
Conversation
6240cda to
0f71084
Compare
634dd67 to
22449b1
Compare
|
65da423 is the start of using bulk insert/update statements in the job manager, and are supposed to be significantly faster than lots of single insert/update statements. I started with rescheduling and job status updates. |
|
@fstagni do you have any view on things to watch out for with bulk inserts and updates, based on previous experience in DIRAC? I can foresee some risks of things becoming inconsistent, which could be mitigated by reducing the batch sizes or carefully checking the input and results of each statement execution. |
…routes for jobs router
Co-authored-by: Chris Burr <chrisburr@users.noreply.github.com>
Working tests
Regenerated REST client with autorest
regenerate client
…schedule_job, eventually will extend to set_job_statuses)
… where possible hold on to comments for later
Overwrite correctly
|
@chrisburr @aldbr once the tests fully pass I think this is ready to merge |
job_managertojobsreschedule_jobto respect the job state machineFor #22
Needs DIRACGrid/DIRAC#7794
closes #22, #341
TODO:
configobject to pull outMaxReschedulingfrom the CS instead of making a property in JobDB