Later, the primary sends transactions to the mirror - but that traffic doesn't slow down your transactions. High performance (asynchronous) - DUI operations are only written to the primary's transaction log, then the transaction is immediately committed.Transactions are inherently slower, but in a perfect world, you won't lose data when you fail over from the primary to the mirror. High safety (synchronous) - every delete/update/insert (DUI) operation is written to the primary's transaction log, sent across the network to the mirror, written to the mirror's transaction log, and then confirmation is sent back to the primary.as part of katello upgrading to pulp-rpm 3.16, we need to support this, and this would give you the ability to ‘mirror content’ without ‘mirroring metadata’, the metadata part which is what imposes many restrictions.There are two modes for database mirroring:.in pulp-rpm 3.16, it is now possible to specify a ‘sync_policy’: REST API for Pulp 3 RPM Plugin which allows us to control these somwhat independently.The error you see was added to make sure that users didnt’ discover these problems after syncing, and instead you get a nice error message. over time it became obvious that piggy backing on this existing option was a mistake, as metadata mirroring was incompatible with a lot of upstream repositories due to various edge cases.So this one option now controls 2 ‘features’, ‘content mirroring’ and ‘metadata mirroring’. When we upgraded, we didn’t realize at the time that this functionality piggy backed on the ‘mirror=true’ option that we call ‘mirror on sync’. Pulp added a metadata mirroring feature as part of pulp-rpm 3.14.Let me kinda summarize the issue and what we’re planning on doing to help Instead of having clients fail when they go looking for deltaRPMs that aren’t there, we added an error to tell users to use a proper sync mode for those repos.īut, as you mention, it really sucks to not have that option available for some repos, so we’re (re)adding a third mode that mirrors the content without mirroring the metadata.
#MIRRORSYNC ERROR TOO MANY CLIENT RECORDS INSTALL#
This repo includes metadata for deltaRPMs, but Pulp doesn’t support deltaRPMs, so clients like yum, DNF, zypper would try to install the deltaRPMs that were not there. The current “mirror” sync tells Pulp to copy and publish all of the original metadata files. Of course, there I cannot even change the mirror setting (though I haven’t tried to republished everything This is something we’re currently working on. I also ran a complete sync on my content proxy and that also showed the same error message (4 times in total). If it’s a limitation of pulpcore I think it should be handled properly in pulpcore that it syncs EPEL without errors.
Of course, there I cannot even change the mirror setting (though I haven’t tried to republished everything first…)īut either way, if it’s a problem in the EPEL repositories they should be notified to fix it. And I also wonder why they do something so weird in EPEL that it breaks with the pulpcore sync. It’s a bummer that it doesn’t work for two of the probably most used repositories in the RHEL/EL universe. In particular for those huge EPEL repositories it’s something I really want. It’s my understanding the mirroring removes old, outdated content which doesn’t exist in the repository anymore. I have disabled “Mirror on Sync” for those two repository although I don’t really like it.
I think this message has been introduced earlier but I guess the error only appears if you do a complete sync and not the optimized one or it only appears now with 3.14.7… This repository uses features which are incompatible with ‘mirror’ sync. Two repositories, however, showed errors: EPEL 7 and EPEL 8 (the normal, not the EPEL 8 Modular repo): I wanted pulpcore 3.14.7 because of Katello 4.1.2.1 - 404 error through content proxy due to incorrect location_hrefĪnyway, to fix possibly broken urls in the database I run a complete sync on all products, i.e. I am running Katello 4.1.4 on CentOS 7 with the latest pulpcore updates installed today.
0 kommentar(er)
