Revert to previous values to limit Express input rate. #4387
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
maxInputEvent determines how many events a single express job is allowed to process (express jobs in principle are multi-lumi). With it you can only force it do go down to a single lumi per job, you cannot fail lumis. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes I mentioned on HN: https://hypernews.cern.ch/HyperNews/CMS/get/tier0-Ops/1720/1/1/1.html
maxInputEvents is 400 because that's what we had before using the workaround. Not sure why it's different from the maxInputRate. Do these two parameters need to be the same?