Skip to content

Job dependencies not propertly tracked for jobs in routing queue #415

Open

Description

@gbeane

If we have jobs in a routing queue waiting for slots to open up in an execution queue (due to max_user_queuable limits), and those jobs have dependencies on jobs already in the execution queue, then the job may get rejected when it does finally route if one or more of the jobs it depends on have already executed and completed. upon routing, job is immediately rejected: "Job rejected by all possible destinations (check syntax, queue resources, ...)"

We need job dependencies to be tracked properly for jobs in routing queues.

Activity

  1. IsItSnowingInSpace commented on Jun 19, 2017

    @IsItSnowingInSpace

    This should be fixed with these commits:

    e3d5fd5
    5507bff

  2. gbeane commented on Jun 29, 2017

    @gbeane
    Author

    that's great!

    When will we see a Torque release with these fixes? We are currently on Torque 6.0.x on our clusters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions