Project

General

Profile

Actions
Copy link

Bug #4844

closed

[Node Manager] Treats min_nodes as min_nodes_idle when job queue is empty

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

Status:
Resolved
Priority:
Normal
Assigned To:
Brett Smith
Category:
Node Manager
Target version:
2015-01-07 sprint
Story points:
1.0

Description

Two Node Manager issues were resolved around the same time: spin up new nodes when current nodes are all busy (#4357), and supporting a min_nodes configuration knob (#4294). Unfortunately, the implementations don't play well together. Because min_nodes is implemented by making sure the server wishlist has at least min_nodes entries, when all up nodes are busy, the daemon believes that it must start a new one to satisfy the wishlist, and does so.

#4299 will require a richer representation of the wishlist anyway, so it might be reasonable to go ahead and do that now to fix this bug.

Subtasks 1 (0 open — 1 closed)

Task #4845: Review (and maybe merge?) 4844-stricter-min-nodes-wipResolvedWard Vandewege12/19/2014Actions
Actions
Copy link
 #1

Updated by Brett Smith over 9 years ago

  • Status changed from New to In Progress
  • Assigned To set to Brett Smith
  • Target version changed from Bug Triage to 2015-01-07 sprint
Actions
Copy link
 #2

Updated by Ward Vandewege over 9 years ago

Thanks, I reviewed and merged this.

Actions
Copy link
 #3

Updated by Brett Smith over 9 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF