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

Provide the ability to do a separate cache-hint for cloning. #6478

Merged

Conversation

bbockelm
Copy link
Contributor

Cloning is one of the very problematic places for high-latency IO
as it reads baskets one-at-a-time. Hence, it makes a lot of sense
to use lazy-download for this case. However, it may not be
desirable to enable lazy-download for all workflows! Nor may it
be desirable for the workflow layers to enable lazy-download for
all merges (as some sites don't have the disk space).

This patch allows us to selectively turn on lazy-download only for
merge jobs at a given site by editing site-local-config.xml.

This commit is a cherry-pick of the b19f156 in 7_3_X.

Cloning is one of the very problematic places for high-latency IO
as it reads baskets one-at-a-time.  Hence, it makes a lot of sense
to use lazy-download for this case.  *However*, it may not be
desirable to enable lazy-download for all workflows!  Nor may it
be desirable for the workflow layers to enable lazy-download for
all merges (as some sites don't have the disk space).

This patch allows us to selectively turn on lazy-download only for
merge jobs at a given site by editing site-local-config.xml.
@cmsbuild
Copy link
Contributor

A new Pull Request was created by @bbockelm (Brian Bockelman) for CMSSW_7_2_X.

Provide the ability to do a separate cache-hint for cloning.

It involves the following packages:

FWCore/Catalog
FWCore/Services
IOPool/Output
IOPool/TFileAdaptor
Utilities/StorageFactory

@cmsbuild, @Dr15Jones, @ktf, @nclopezo can you please review it and eventually sign? Thanks.
@wddgit, @wmtan this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@Dr15Jones
Copy link
Contributor

@bbockelm can you add a 'link' to the pull request in CMSSW_7_3_X from which this came? That will help in later archeology :).

@bbockelm
Copy link
Contributor Author

Greetings, future archeologists! This was previously known as #5983

@Dr15Jones
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_2_X IBs unless changes or unless it breaks tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar

@Dr15Jones
Copy link
Contributor

@bbockelm This is to deal with the problem seen that the Tier 0, correct?

@bbockelm
Copy link
Contributor Author

@Dr15Jones - correct.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_2_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_2_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar

@davidlange6
Copy link
Contributor

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants