Bug #11166

[Crunch2] crunchrun.go should avoid name collisions when creating log collections

Added by Lucas Di Pentima 10 months ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
02/24/2017
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
0.5

Subtasks

Task #11196: Review 11166-log-name-collisionResolvedPeter Amstutz

Task #11212: use ensure_unique_name flag or timestampResolvedTom Clegg


Related issues

Related to Arvados - Bug #11190: Containers seem to run more than once, which isn't supposed to happenResolved2017-03-01

Associated revisions

Revision a1b01498
Added by Tom Clegg 9 months ago

Merge branch '11166-log-name-collision'

closes #11166

History

#1 Updated by Tom Morris 10 months ago

  • Subject changed from cruchrun.go should avoid name collisions when creating log collections to [Crunch2] crunchrun.go should avoid name collisions when creating log collections
  • Target version set to 2017-03-15 sprint

#2 Updated by Lucas Di Pentima 10 months ago

We've been seeing CR logs with messages like this:

2017-03-01T17:31:40.739323663Z While creating log collection: arvados API server error: #<PG::UniqueViolation: ERROR:  duplicate key value violates unique constraint "index_collections_on_owner_uuid_and_name" 
2017-03-01T17:31:40.739323663Z DETAIL:  Key (owner_uuid, name)=(tb05z-tpzed-000000000000000, logs for tb05z-dz642-eie1eal1059y9bb) already exists.

If for some reason the process quits after writing the log collection, the next time that is retried, it will cause a PG::UniqueViolation error.

#3 Updated by Tom Clegg 10 months ago

Should be a matter of using the ensure_unique_name flag.

#4 Updated by Tom Clegg 10 months ago

  • Assigned To set to Tom Clegg

#5 Updated by Tom Clegg 10 months ago

  • Story points set to 0.5

#6 Updated by Tom Clegg 9 months ago

  • Status changed from New to In Progress

#7 Updated by Peter Amstutz 9 months ago

LGTM.

#8 Updated by Tom Clegg 9 months ago

11166-log-name-collision @ cb0b666f86ce87d35667e8e23e3775b703a37841

#9 Updated by Tom Clegg 9 months ago

  • Status changed from In Progress to Resolved

Applied in changeset arvados|commit:a1b0149879593df786807afbefb26d4687ebe161.

Also available in: Atom PDF