New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DAS dataset runs query shows runs with no valid files #57

Open

germanfgv opened this issue Aug 15, 2023 · 0 comments

germanfgv commented Aug 15, 2023 •

edited

Loading

Users have noticed that after file invalidations, DAS still displays blocks and dataset runs data as if the files were still there

Lets use dataset /DisplacedJet/Run2023C-PromptReco-v2/MINIAOD as an example.
This dataset initially included files from run 367661, but they were all invalidated, as can be seen here:
https://cmsweb.cern.ch/das/request?view=list&limit=50&instance=prod%2Fglobal&input=file+dataset%3D%2FDisplacedJet%2FRun2023C-PromptReco-v2%2FMINIAOD+run%3D367661

Nonetheless, run 367661 still appears in DAS as belonging to the dataset:
https://cmsweb.cern.ch/das/request?view=list&limit=50&instance=prod%2Fglobal&input=run+dataset%3D%2FDisplacedJet%2FRun2023C-PromptReco-v2%2FMINIAOD

This issue is already being addressed by a new DBS development:
dmwm/dbs2go#99

As DAS default behaviour is to only show valid files, it needs to be adjusted so it uses the new capabilities of the DBS API

FYI: @vkuznet @d-ylee

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment