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

dcache: reject access to files with nearline QoS #7676

Merged
merged 1 commit into from
Oct 9, 2024

Conversation

kofemann
Copy link
Member

@kofemann kofemann commented Oct 9, 2024

Motivation:
If file has QoS policy "HSM-only" then dCache should reject the access to the file, even if file is still available on disk (as transition might take some time).

Modification:

  • Update QoS policy engine to reflect policy in the namespace attributes
  • Update Transfer to request policy state (as an indicate of applied policy) and reject read transfers if access latency is nearline.

Result:
dCache behavior compliant with selected QoS policy.

Acked-by: Lea Morschel
Acked-by: Dmitry Litvintsev
Target: master
Require-book: no
Require-notes: yes
(cherry picked from commit 1a3c12e)

Motivation:
If file has QoS policy "HSM-only" then dCache should reject the access
to the file, even if file is still available on disk (as transition
might take some time).

Modification:
- Update QoS policy engine to reflect policy in the namespace attributes
- Update Transfer to request policy state (as an indicate of applied
  policy) and reject read transfers if access latency is nearline.

Result:
dCache behavior compliant with selected QoS policy.

Acked-by: Lea Morschel
Acked-by: Dmitry Litvintsev
Target: master
Require-book: no
Require-notes: yes
(cherry picked from commit 1a3c12e)
Signed-off-by: Tigran Mkrtchyan <[email protected]>
@lemora lemora merged commit 1e916a9 into dCache:10.2 Oct 9, 2024
1 check passed
@kofemann kofemann deleted the qos-10.2 branch October 10, 2024 06:34
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

Successfully merging this pull request may close these issues.

2 participants