Project

General

Profile

Actions

Bug #15946

closed

[crunch-run] [collectionfs] Deadlock while writing output collection

Added by Tom Clegg about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Story points:
-
Release relationship:
Auto

Description

Running several similar containers, some succeeded but some got stuck while writing the final output collection. The log indicates all of the expected files were written to collectionfs ("copying ... (... bytes)") but the finished collection was never saved.


Subtasks 1 (0 open1 closed)

Task #15947: Review 15946-collectionfs-deadlockResolvedTom Clegg12/23/2019Actions

Related issues 2 (0 open2 closed)

Related to Arvados - Bug #15928: Deadlock in crunch-run testsResolvedTom Clegg12/11/2019Actions
Related to Arvados - Bug #15910: [crunch-run] Crash while writing output filesResolvedTom Clegg12/04/2019Actions
Actions #1

Updated by Tom Clegg about 5 years ago

Found a case where commitBlock would set a "flushing in progress" flag on a segment, but then return early (and never indicate
it was done) because a different segment had another flush in progress. Once that happened, sync operations like MarshalManifest would block forever.

15946-collectionfs-deadlock @ c05caa378debd04205690c6cb96508e4e7fb6c8b -- developer-run-tests: #1700

Actions #2

Updated by Tom Clegg about 5 years ago

  • Related to Bug #15928: Deadlock in crunch-run tests added
Actions #3

Updated by Tom Clegg about 5 years ago

  • Related to Bug #15910: [crunch-run] Crash while writing output files added
Actions #4

Updated by Lucas Di Pentima almost 5 years ago

This LGTM, thanks!

Actions #5

Updated by Anonymous almost 5 years ago

  • % Done changed from 0 to 100
  • Status changed from In Progress to Resolved
Actions #6

Updated by Peter Amstutz almost 5 years ago

  • Target version changed from 2020-01-15 Sprint to 2020-01-02 Sprint
Actions

Also available in: Atom PDF