-
Notifications
You must be signed in to change notification settings - Fork 111
Set up CVMFS alien cache on NFS #1839
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
Changes from all commits
b6aef05
c22798f
83d5213
ebb4f0c
673f620
2dbeb2b
765b591
de537c3
aeccbf5
8954203
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| cvmfs_role: client | ||
|
|
||
| cvmfs_params: | ||
| CVMFS_MEMCACHE_SIZE: 256 | ||
|
|
||
| CVMFS_CACHE_PRIMARY: cvmfs | ||
|
|
||
| CVMFS_CACHE_cvmfs_TYPE: tiered | ||
| CVMFS_CACHE_cvmfs_UPPER: disk | ||
| CVMFS_CACHE_cvmfs_UPPER_READONLY: no | ||
| CVMFS_CACHE_cvmfs_LOWER: nfs | ||
| CVMFS_CACHE_cvmfs_LOWER_READONLY: no | ||
gsaudade99 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| CVMFS_CACHE_disk_TYPE: posix | ||
| CVMFS_CACHE_disk_QUOTA_LIMIT: 5000 | ||
|
|
||
| CVMFS_CACHE_nfs_TYPE: posix | ||
| CVMFS_CACHE_nfs_ALIEN: /data/cvmfs08/cache/ | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I noticed this should be rewritten in terms of variables from the |
||
| CVMFS_CACHE_nfs_SHARED: no | ||
| CVMFS_CACHE_nfs_QUOTA_LIMIT: -1 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I understand correctly, we need to provide a share, that is >= all cvmfs repos that we mount?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's only needed if However, an alien cache cannot join the shared cache (see docs),
probably because CVMFS lacks an adequate synchronization mechanism to manage the quota in a distributed system. That's also why a script to manage the size of this cache would be needed. |
||
|
|
||
| galaxy_cvmfs_repos_enabled: config-repo | ||
| galaxy_cvmfs_server_urls: | ||
| - domain: galaxyproject.org | ||
| urls: | ||
| - 'http://cvmfs1-ufr0.galaxyproject.eu/cvmfs/@fqrn@' | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
at this point sn09 could even use
memorywe have 300G of unused RAMUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this parameter only sets the name for the "Upper" cache manager instance
https://cvmfs.readthedocs.io/en/stable/cpt-configure.html#tiered-cache
From how I understand the docs without a plugin there is only
posix.However they recommend to set
CVMFS_MEMCACHE_SIZE=256(MB). Maybe we can also do that (or increase it even more)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They have an example how to use memory here
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given this comment, if at the moment there seem to be no issues every time a container job is launched let's leave the
memorycache for a later stage if the need arises.If
CVMFS_MEMCACHE_SIZEis "independent" from the tiered cache system, then let's increase it. Although I am not sure it will have an effect even if "it works", since they only recommend it for pure NFS deployments.