Skip to content
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.

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

new component Tier0Auditor #1961

Closed
hufnagel opened this issue Jul 15, 2011 · 8 comments
Closed

new component Tier0Auditor #1961

hufnagel opened this issue Jul 15, 2011 · 8 comments
Assignees

Comments

@hufnagel
Copy link
Member

The new component Tier0Auditor will handle all the processing checks and advancements for data/work that is inside the Tier0.

  1. Closing runs and lumis

Consistency checks against the StorageManager and T0AST databases to determine whether we have complete data for lumis and runs. We should forget about the currently used closeout code and only port the still to be deployed new system based on the EoR and EoLS records from the StorageManager.

  1. Check completion of split processed streamer lumis

Streamer files can be processed in units smaller than a lumi section (normal for express, error overflow case for repack). Special accounting is done to track when all streamers for a lumi are fully processed.

  1. Run closeout advancement checks

Checks conditions for advancing run state and changes the run state if conditions are met.

  1. Release runs for Express

Determine if express processing for run can start (PopConLogDB check).

  1. Release runs for PromptReco

Determine if PromptReco for run can start (simple timeout).

@hufnagel
Copy link
Member Author

hufnagel: Code (including database code) all exists in the current Tie0 As with the other component, it should be reviewed and possibly simplified/improved when it is moved over. All database related code should also be switched to DAOs for uniformity reasons.

@drsm79
Copy link

drsm79 commented Aug 17, 2011

metson: Milestone T0 2_0_0 deleted

@hufnagel
Copy link
Member Author

hufnagel: Limit the scope of this ticket and only port over the EoR/EoLS based run/lumi closeout code and the code dealing with completion checks of split processed streamer lumis.

Rest of the issues are tracked in other tickets.

@hufnagel
Copy link
Member Author

hufnagel: Limit this ticket further, as lumi closing needs to be handled in the Tier0Feeder (tracked in #3109). Run closing stays in the Tier0Auditor for now, but there is a possibility it'll also move to the Tier0Feeder.

@hufnagel
Copy link
Member Author

hufnagel commented Feb 8, 2012

hufnagel: All run and lumi closeout needs to be handled in the Tier0Feeder, there are just too many dependencies, interconnection and potentials for race conditions to split this up.
So what's left in the end for this component is:

Check completion of split processed streamer lumis
Release runs for Express
Release runs for PromptReco

There might be more eventually, but for now this reduces the priority of this ticket.

@hufnagel
Copy link
Member Author

hufnagel commented Feb 8, 2012

hufnagel: Another think that might go here is closing the run/dataset input fileset for PromptReco. This might be a no-op though because the repacking might close it's output fileset automatically when it's finished.

@hufnagel
Copy link
Member Author

hufnagel commented May 3, 2012

hufnagel: Not sure this is needed any longer at all, will put everything into the Tier0Feeder for now. It simplifies things and there does not seem to be any performance issue that would force us to split this up.

@hufnagel
Copy link
Member Author

hufnagel commented May 6, 2012

hufnagel: Template component exists, but with no functionality. Everything it was supposed to do is handled by the Tier0Feeder for now. No reason to change this unless we want to split it across two components for performance reasons.

@ghost ghost assigned hufnagel Jul 24, 2012
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants