You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We had a request which had multiple workflows writing to the same output [1]. For this output, I saw that MSOutput created 2 tape rules most probably because there were multiple workflows producing the same output:
That is an interesting case that I had never thought about.
If we want to ensure a single tape rule for each output dataset, we need to add extra logic to MSOutput to check if there is any Tape rule (under wmcore_output account). In case we find a rule, we can either:
a) skip the Tape rule creation; or
b) proceed with the Tape rule creation, but make sure it goes to the same Tape RSE. This way, it will hit a duplicate rule condition and just reuse the previous rule id.
Impact of the bug
MSOutput
Describe the bug
We had a request which had multiple workflows writing to the same output [1]. For this output, I saw that MSOutput created 2 tape rules most probably because there were multiple workflows producing the same output:
[1] https://dmytro.web.cern.ch/dmytro/cmsprodmon/workflows.php?prep_id=task_BPH-GenericNoSmearGEN-00001
How to reproduce it
Create multiple workflows which share the same prepid and write to the same output and let MSOutput handle their output placement.
Expected behavior
MSOutput should create a single tape rule for a given output dataset regardless of how many workflows produce it
Additional context and error message
I'll delete the FNAL tape rule. Is this going to create issues for workflow archival?
The text was updated successfully, but these errors were encountered: