Story #9626

[Crunch2] c-d-slurm should avoid new --priority option

Added by Brett Smith over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Brett Smith
Category:
Crunch
Target version:
Start date:
07/18/2016
Due date:
% Done:

100%

Estimated time:
Story points:
0.5

Description

crunch-dispatch-slurm translates the container's priority into the sbatch --priority option. According to the news, this option was added in 14.03.2, which is probably too new for us to require (it's not even included Ubuntu trusty, supported until 2019).

It's also not clear to me that we want it at all. The man page says, "Only Slurm operators and administrators can set the priority of a job." It's not clear to me that crunch-dispatch-slurm should need to count on having those privileges. Even if it happens to have them, I'm not sure it should use what is apparently such a blunt instrument.


Related issues

Related to Arvados - Story #9187: [Crunch2] Update dispatcher to use new API supportResolved05/02/2016

Associated revisions

Revision c0eb54ea (diff)
Added by Brett Smith over 3 years ago

9262: Stop setting sbatch --priority in crunch-dispatch-slurm.

There are a few reasons we want to back this out:

  • `--priority` is a relatively new feature of SLURM, added in 14.03,
    and it's not clear how many users are running that.
  • Setting `--priority` requires extra privileges, per the sbatch man
    page, and it's not clear crunch-dispatch-slurm should run with
    those.
  • There are multiple ways to set the "priority" of a SLURM job.
    There's also a niceness value. Which is correct to use is probably
    ultimately going to depend on site rules or conventions. We need to
    get more feedback on what people are doing before we implement
    something. We might need configurations options along the lines of
    "translate container priority into this option with this scaling
    factor," or something like that.

Per discussion with Tom Clegg. Closes #9626.

History

#1 Updated by Brett Smith over 3 years ago

  • Subject changed from [Crunch2] c-d-slurm uses new --priority option to [Crunch2] c-d-slurm should avoid new --priority option

#2 Updated by Brett Smith over 3 years ago

  • Target version set to Arvados Future Sprints

#3 Updated by Brett Smith over 3 years ago

  • Status changed from New to In Progress
  • Assigned To set to Brett Smith
  • Target version changed from Arvados Future Sprints to 2016-07-20 sprint
  • Story points set to 0.5

#4 Updated by Brett Smith over 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset arvados|commit:c0eb54eaffd1dac69f4ea73742a69a2473669538.

#5 Updated by Brett Smith over 3 years ago

Discussed with Tom and agreed to remove --priority. See the commit message for rationale.

Also available in: Atom PDF