-
Notifications
You must be signed in to change notification settings - Fork 248
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
[batch] Add ability to create job groups at top level #14170
Closed
Closed
Changes from all commits
Commits
Show all changes
77 commits
Select commit
Hold shift + click to select a range
80b664a
[batch] Finalize job groups in database
jigold 0b50b03
fix
jigold 6c9c776
fix for ambig column
jigold 284b457
fix foreign key constraint
jigold d1fd11a
dont lock primary key updates
jigold 8ac5425
fix cancel job group
jigold 5ffa578
last fix?
jigold 03cdaa5
get rid of extra complexity
jigold 904a045
fixup estimated-current.sql
jigold 3bdca11
fix cancel child job groups
jigold e7fe638
add new index
jigold e09c512
add back batch updates fields
jigold b40bff2
[batch] Use job group id in front end and driver queries
jigold 1e20595
address comments
jigold ed95628
get rid of exposing job group id to worker
jigold e6ed1f0
address comments
jigold 853d949
delint
jigold 4c2b750
Merge commit '24525adb9c09a73a1ae820c9945acd35299878ed' into thread-j…
jigold d7d3b53
Merge commit 'fa2ef0f2c76654d0c037ff6db60ccb8842fb8539' into thread-j…
jigold 1dc4ce9
partial ruff apply
jigold b777802
partial ruff apply
jigold 295c339
[batch] Add job group in client and capability to list and get job gr…
jigold 166928c
wip
jigold 322b01d
fix
jigold f1697c2
delint
jigold 0d97818
delint
jigold 0f2cc55
[batch] Add ability to create job groups at top level only
jigold 5fbd6e8
minor fixes
jigold 9b17076
minor fixes
jigold 239bd86
bad rebase fix
jigold 9889031
fixing bad rebase
jigold 937d501
finish fixing rebase
jigold d32e968
addressed most of front end comments
jigold 328e7a6
refactored bunching
jigold 26fe167
add update id default to 1
jigold 0b1b66b
more front end changes
jigold 9555687
more changes
jigold 8a468ba
addressing more comments
jigold 8aa3bb8
lots of comments addressed
jigold f3b6e4c
add ability to create jobs
jigold c3b825f
fix tests
jigold 36af4f8
more fixes
jigold 7bb3f2b
ruff check
jigold 0802a8e
ruff format
jigold d631d70
delint client
jigold 3597a89
final delint
jigold 1030f59
fix index and various bugs
jigold 229d8b6
fix database error in commit_batch_update
jigold fc781a6
attempt to fix mjc
jigold ef6163c
fix ambig field
jigold 9fd31c3
wip
jigold 4569b3d
cleanup db code
jigold 4219370
fix mjc missing var
jigold 9a9610f
turn off updating attempts to try and debug
jigold 1336950
process of elimination
jigold f66f615
actually have new triggers in database
jigold 56f6c77
fix build.yaml
jigold 3ffdfae
modify commit_batch_update
jigold 823da60
recursive job group state n_jobs and no migration transaction
jigold df9ebcd
fix cancel_job_group
jigold f76070d
more fixes
jigold ae1b484
fix python front end icr
jigold 51242a0
fix bad global var collision
jigold b138287
fix cancel
jigold c63f961
fix cancel
jigold 490cff2
turn off unschedule job in canceller
jigold e67594f
get rid of committed check
jigold e50ab12
dont unschedule jobs in canceller
jigold 2fdfcfc
recursive populate jg_inst_coll_cancellable_resources
jigold aacfddb
test_job_group_cancel_after_n_failures_does_not_cancel_higher_up_jobs…
jigold 16187ca
fix test
jigold 964dcfa
in sync sql
jigold 244354a
delint
jigold c4028c1
get state right in commit
jigold 946ef12
get rid of unsed columns in staging table
jigold 1870039
more fixes
jigold de473d5
add nested job groups
jigold File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,3 @@ | ||
ROOT_JOB_GROUP_ID = 0 | ||
|
||
MAX_JOB_GROUPS_DEPTH = 5 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does this do a Python-side filter rather than a SQL-side filter like the next query?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's two types of cancelled jobs. One is for cancelled job groups / batches in which all jobs that are not always run are cancelled. But then there's cancellation of individual jobs if their parent's failed. I'm guessing it was setup this way with two separate queries due to optimizing speed and being able to use the
remaining
share variable. I can see if there's a way to optimize it into 1 query if that's something you want to see happen.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And this only applies to ready jobs -- not creating or running jobs.