Project

General

Profile

Actions
Copy link

Bug #5381

closed

[Crunch] Node went away unexpectedly during pipeline run.

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

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Node Manager
Target version:
-
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 1 (0 open — 1 closed)

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

Updated by Peter Amstutz almost 10 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Tom Clegg almost 10 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.

Actions
Copy link
 #3

Updated by Tom Clegg almost 10 years ago

  • Category set to Node Manager
Actions
Copy link
 #4

Updated by Tom Clegg almost 10 years ago

  • Target version changed from Bug Triage to 2015-04-29 sprint
Actions
Copy link
 #5

Updated by Ward Vandewege over 9 years ago

  • Story points set to 0.5
Actions
Copy link
 #6

Updated by Tom Clegg over 9 years ago

  • Target version changed from 2015-04-29 sprint to Arvados Future Sprints
Actions
Copy link
 #7

Updated by Ward Vandewege about 4 years ago

  • Status changed from New to Closed
Actions
Copy link
 #8

Updated by Ward Vandewege about 4 years ago

  • Target version deleted (Arvados Future Sprints)
Actions
Copy link

Also available in: Atom PDF