Project

General

Profile

Bug #21413

datasets generated for dependent job launches should be more restrictive.

Added by Marc Mengel almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
11/21/2018
Due date:
% Done:

100%

Estimated time:
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

We are getting situations, usually when a user cancels a submission after some files have been generated, that the dependent stage of the next submission get both files from this launch and from the cancelled one, leading to duplication.

To fix this, we should add a check on creation time on the dataset definition, that it is later than the start of the submission. This will eliminate the problem, as long as files get their metadata declared in the job. If files are being declared later, say by an FTS, then we could still get some overlap here, but it does give us a recipe to give users to avoid it entirely.

History

#1 Updated by Marc Mengel almost 2 years ago

  • Status changed from New to Resolved
  • Assignee set to Marc Mengel

Implemented in 49cf4307

asked for create_time > submission create time in the dataset definition.

#2 Updated by Marc Mengel almost 2 years ago

  • % Done changed from 0 to 100

#3 Updated by Stephen White over 1 year ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF