When we work through the list of containers in an alphabetical fashion,
we end up duplicating much of the layer fetching because it can occur at
the same time. Things like cinder-api, cinder-backup, cinder-volume
share many of the same layers. Since we don't ensure that we only do
a single fetching of a layer hash durring the multiprocessing, we end
up duplicating the fetches of layers. By randomizing the fetches, we
reduce the likelihood that we'll be fetching the same family of service
containers concurrently.
Change-Id: Ifbcd55de52c9e2283203b1c6e2adeb266d43eca6
Related-Bug: #1844446
(cherry picked from commit 3adfefa13aebd7bd9e48c952df9107d51a557011)
Reviewed: https:/ /review. opendev. org/686785 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=0c3c2623de8 418ad7470d2369c 26f27ef651aefc
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 0c3c2623de8418a d7470d2369c26f2 7ef651aefc
Author: Alex Schultz <email address hidden>
Date: Thu Sep 26 11:05:15 2019 -0600
Randomize the container list for uploads
When we work through the list of containers in an alphabetical fashion,
we end up duplicating much of the layer fetching because it can occur at
the same time. Things like cinder-api, cinder-backup, cinder-volume
share many of the same layers. Since we don't ensure that we only do
a single fetching of a layer hash durring the multiprocessing, we end
up duplicating the fetches of layers. By randomizing the fetches, we
reduce the likelihood that we'll be fetching the same family of service
containers concurrently.
Change-Id: Ifbcd55de52c9e2 283203b1c6e2ade b266d43eca6 d9e48c952df9107 d51a557011)
Related-Bug: #1844446
(cherry picked from commit 3adfefa13aebd7b