Actions
Bug #15946
closed
[crunch-run] [collectionfs] Deadlock while writing output collection
Story points:
-
Release:
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.
Related issues
Updated by Tom Clegg almost 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
Updated by Tom Clegg almost 5 years ago
- Related to Bug #15928: Deadlock in crunch-run tests added
Updated by Tom Clegg almost 5 years ago
- Related to Bug #15910: [crunch-run] Crash while writing output files added
Updated by
Updated by Anonymous almost 5 years ago
- % Done changed from 0 to 100
- Status changed from In Progress to Resolved
Applied in changeset arvados|949abe8b7922c2b8d74b40366f053fdab1a1d214.
Updated by Peter Amstutz almost 5 years ago
- Target version changed from 2020-01-15 Sprint to 2020-01-02 Sprint
Actions