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

[Michael Hrivnak]

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> 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
> https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20160701/14e8197a/attachment.htm>