Story #12574
closed
[API] Propagate priority of parent container to children
Added by Tom Morris about 7 years ago.
Updated about 7 years ago.
Estimated time:
(Total: 0.00 h)
Description
Propagate from the requesting container to children.
A committed container request's priority should be no less than the priority of its requesting container, if any. Priority should be updated when the requesting container's priority changes.
- Tracker changed from Bug to Story
- Subject changed from Propagate priority of parent job (a-c-r) to children to [API Server] Propagate priority of parent job (a-c-r) to children
- Description updated (diff)
- Story points set to 1.0
- Target version changed from To Be Groomed to Arvados Future Sprints
- Target version changed from Arvados Future Sprints to 2017-12-06 Sprint
- Assigned To set to Lucas Di Pentima
- Subject changed from [API Server] Propagate priority of parent job (a-c-r) to children to [API] Propagate priority of parent container to children
- Description updated (diff)
- Related to Story #12552: When priority is equal, the children of an earlier-submitted workflow should run first added
- Status changed from New to In Progress
- Assigned To changed from Lucas Di Pentima to Peter Amstutz
Just one suggestion: how about renaming update_priority to something more descriptive, like propagate_priority or update_children_priority. The code LGTM. Thanks!
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by Tom Morris 
Updated by 
Updated by 
Updated by 
Updated by Anonymous