[Pulp-list] Long upgrade times from 2.6 -> 2.8

[Ashby, Jason (IMS)]

FWIW I just upgraded from 2.7 -> 2.8 and it was approx. 1-2 hr upgrade to get through the migrations in pulp-manage-db.

290 GB /var/lib/pulp
16 GB MongoDB

From: pulp-list-bounces at redhat.com [mailto:pulp-list-bounces at redhat.com] On Behalf Of Michael Hrivnak
Sent: Friday, July 01, 2016 8:31 AM
To: Eric Helms <ehelms at redhat.com>
Cc: pulp-list <pulp-list at redhat.com>
Subject: Re: [Pulp-list] Long upgrade times from 2.6 -> 2.8

Did you get any feedback on whether one particular migration seemed to be running for a lot of that time?

Michael

On Fri, Jul 1, 2016 at 7:23 AM, Eric Helms <ehelms at redhat.com<mailto:ehelms at redhat.com>> wrote:
Howdy,

We (Katello) have had users reporting incredibly long upgrade times when upgrading from 2.6 to 2.8. This occurs during the pulp-manage-db step that is run as the beginning of our installers upgrade process. Based on the numbers below, does this make sense at all?

Some numbers:

18 hour upgrade
1.5 TB /var/lib/pulp
100GB MongoDB


Thanks,
Eric

_______________________________________________
Pulp-list mailing list
Pulp-list at redhat.com<mailto:Pulp-list at redhat.com>
https://www.redhat.com/mailman/listinfo/pulp-list


________________________________

Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20160701/6ead58cc/attachment.htm>