Bug 1174392 - [RFE] sync_with_auto_publish skip publishing if nothing new from sync
Summary: [RFE] sync_with_auto_publish skip publishing if nothing new from sync
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: rpm-support
Version: unspecified
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-15 19:15 UTC by tlynch
Modified: 2015-02-28 23:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: For auto_publish, do publish only if sync found changes Reason: Publish generates repo metadata which consumes CPU and IO but new version of published repo is the same content as prior version. Sync frequency is limited by publish task time. Result: Able to publish changes in source yum repo more frequently. Frequency is currently limited by time taken to publish. If publish only happens when changes are noticed then less CPU and IO are consumed and source repo can be polled for changes more frequently.
Clone Of:
Environment:
Last Closed: 2015-02-19 01:20:58 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 281 0 None None None Never

Description tlynch 2014-12-15 19:15:39 UTC 
I notice pulp does a lot of work when syncing and publishing a yum repo even when there are no new packages in the source repo and the source yum metadata has not changed. I have a large yum repo that needs to be kept current on pulp so it is scheduled to sync and publish on a low interval, 5 minutes. The source repo is large, >7k packages, but pulp does a publish every time the schedule runs even though nothing has been added or removed from the repo.
Comment 1 Brian Bouterse 2015-02-19 01:20:58 UTC 
Moved to https://pulp.plan.io/issues/281
Note You need to log in before you can comment on or make changes to this bug.