Refactor #30828
Actions::Katello::Repository::IndexContent is performed even on repositories that have not changed
Pull request:
Fixed in Releases:
Found in Releases:
Description
On large Content View publishes, a good portion of the publish is spent running Actions::Katello::Repository::IndexContent. In cases where repositories do not change, we still run IndexContent.
This slows down users who desire rapid publishes with only a small set of changes, eg:
- OS repos with 1000s of packages never change
- app layer repos with few packages that change often
Users have to pay the price to index the content on a publish for the large OS repos that are largely static.
How to reproduce:
1) Create content view with RPM content
2) Publish CV, note IndexContent steps are run
3) Publish CV again with no changes, note IndexContent is still run.
Associated revisions
History
#1
Updated by Mike McCune over 1 year ago
also, would we expect re-indexing to take 300+ seconds?
1167: Actions::Katello::Repository::IndexContent (success) [ 340.71s / 340.71s ] Queue: default Queue: default Started at: 2020-09-12 20:59:08 UTC Ended at: 2020-09-12 21:04:49 UTC Real time: 340.71s
#2
Updated by James Jeffers over 1 year ago
- Triaged changed from No to Yes
- Target version set to Katello 3.18.0
#3
Updated by Jonathon Turel over 1 year ago
- Category set to Repositories
#4
Updated by The Foreman Bot over 1 year ago
- Assignee set to James Jeffers
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/9036 added
#5
Updated by Jonathon Turel over 1 year ago
- Target version changed from Katello 3.18.0 to Katello 4.0.0
#6
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases Katello 4.1.0 added
#7
Updated by James Jeffers over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|8f5436dff5eac43274b79003daa1c656de835ffe.
Fixes #30828 - check for matching content and use outcome as contents changed input for content index