Bug #5381

[Crunch] Node went away unexpectedly during pipeline run.

Added by Peter Amstutz about 4 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Node Manager
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
0.5

Description

In pipeline 4xphq-d1hrv-rfu9kj37vmke3dh the first two jobs use compute9, then compute9 goes away unexpectedly before the 3rd job can run. After a bit, a new node comes up (compute7) and runs the last job. Explain what happened to compute9.


Related issues

Related to Arvados - Bug #5383: [API] API server should always retrieve current time from database, never Time.now()Resolved03/16/2015

History

#1 Updated by Peter Amstutz about 4 years ago

  • Description updated (diff)

#2 Updated by Tom Clegg about 4 years ago

Is there a minimum idle time a node must have reached in order to get killed off by node manager during its shutdown window? If not (or if it's short) perhaps that's the explanation/fix we're looking for.

#3 Updated by Tom Clegg about 4 years ago

  • Category set to Node Manager

#4 Updated by Tom Clegg about 4 years ago

  • Target version changed from Bug Triage to 2015-04-29 sprint

#5 Updated by Ward Vandewege about 4 years ago

  • Story points set to 0.5

#6 Updated by Tom Clegg about 4 years ago

  • Target version changed from 2015-04-29 sprint to Arvados Future Sprints

Also available in: Atom PDF