-
Notifications
You must be signed in to change notification settings - Fork 18
4th queue to expedite high priority requests #1096
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
Comments
Updated jira to clarify the priority for the proposed new queue. |
nataliaratnikova
added a commit
that referenced
this issue
Oct 3, 2017
in PHEDEX.Nextgen.Request.Xfer, see #1096
nataliaratnikova
added a commit
that referenced
this issue
Oct 3, 2017
nataliaratnikova
added a commit
that referenced
this issue
Oct 5, 2017
nataliaratnikova
added a commit
that referenced
this issue
Oct 5, 2017
nataliaratnikova
added a commit
that referenced
this issue
Oct 5, 2017
getTransferQueue and updateSubscription functions see #1096 .
nataliaratnikova
added a commit
that referenced
this issue
Oct 5, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
following up from https://its.cern.ch/jira/browse/CMSCOMPPR-1243 can we deploy a 4th queue that will be left empty at all times until we need to expedite something.
The text was updated successfully, but these errors were encountered: