Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
cta
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Harbor Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
dCache
cta
Commits
a1de4854
Commit
a1de4854
authored
8 years ago
by
Steven Murray
Browse files
Options
Downloads
Patches
Plain Diff
Fixed third reviewer comment - Does this mean the background task is resumed
parent
2308d239
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/CHEP2016/CHEP_2016_paper_CTA.pdf
+0
-0
0 additions, 0 deletions
doc/CHEP2016/CHEP_2016_paper_CTA.pdf
doc/CHEP2016/CHEP_2016_paper_CTA.tex
+5
-4
5 additions, 4 deletions
doc/CHEP2016/CHEP_2016_paper_CTA.tex
with
5 additions
and
4 deletions
doc/CHEP2016/CHEP_2016_paper_CTA.pdf
+
0
−
0
View file @
a1de4854
No preview for this file type
This diff is collapsed.
Click to expand it.
doc/CHEP2016/CHEP_2016_paper_CTA.tex
+
5
−
4
View file @
a1de4854
...
...
@@ -304,10 +304,11 @@ adjustments are expected as experience with CTA grows.
\subsection
{
Tape drive pre-emption
}
A background task that repacks or verifies a whole tape can take several hours.
Such long duration background tasks must be pre-empted when higher priority user
tasks arrive in order to meet the latency requirements of users. The tape
daemon will keep polling the scheduling information at a low rate and interrupt
a low priority background task if a higher priority one is available to replace
it.
tasks arrive in order to meet the latency requirements of users. A pre-empted
background task will be resumed at a later point in time when it again becomes
the highest priority task. The tape daemon will keep polling the scheduling
information at a low rate and interrupt a low priority background task if a
higher priority one is available to replace it.
This mixing of high and low priority tasks previously had to be handled by hand or
\textit
{
ad hoc
}
scripts in CASTOR.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment