Project

General

Profile

Actions
Copy link

Bug #5917

closed

Node Manager did not spin up enough nodes when I set min_nodes = 20

Added by Bryan Cosca almost 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-

Description

Job qr1hi-8i9sb-6hfkeo7gvpexcjw has been queued for 6.5 hours. When I logged in last night, there were 18 nodes idle and the job still did not run.

Files

nodemanagerdidnotspinupenoughnodes.png (43.1 KB) nodemanagerdidnotspinupenoughnodes.png Bryan Cosca, 05/06/2015 03:03 AM

Related issues 2 (0 open — 2 closed)

Related to Arvados - Bug #4129: [Node Manager] Don't reuse node table recordsClosedActions
Related to Arvados - Bug #5842: [Node Manager] Too many nodes being startedResolvedBrett Smith05/06/2015Actions
Actions
Copy link
 #1

Updated by Brett Smith almost 10 years ago

  • Status changed from New to Closed

Closing as a sort of duplicate. This situation is caused by two bugs we already have filed, #4129 and #5824. #5824 causes 20-node jobs to use more than half of the nodes that Arvados clusters are currently configured to handle. With all that room taken up, #4129 gets us into a situation where we can't create more nodes. Both need to be fixed. #5824 is a high priority right now because it's costing us money.

Actions
Copy link

Also available in: Atom PDF