Project

General

Profile

Actions

Story #2880

closed

Component/job can specify minimum memory and scratch space for worker nodes, and Crunch enforces these requirements at runtime

Added by Tom Clegg about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Brett Smith
Category:
-
Start date:
06/05/2014
Due date:
% Done:

100%

Estimated time:
(Total: 17.00 h)
Story points:
3.0

Description

Implement runtime constraints

The runtime constraints are currently specced as:

  • min_ram_mb_per_node - The amount of RAM (MiB) available on each Node.
  • min_scratch_mb_per_node - The amount of disk space (MiB) available for local caching on each Node.

For now, crunch-dispatch should start the biggest job that it can given the Nodes that are currently available.


Subtasks 4 (0 open4 closed)

Task #2967: Compute nodes report resource information in pingsResolvedBrett Smith06/05/2014

Actions
Task #2975: Review 2880-compute-ping-statsResolvedBrett Smith06/05/2014

Actions
Task #2993: Review 2880-crunch-dispatch-node-constraints-wipResolvedBrett Smith06/06/2014

Actions
Task #2976: Crunch only starts jobs when hardware constraints are satisfiedResolvedBrett Smith06/05/2014

Actions
Actions

Also available in: Atom PDF