On Wed, Mar 20, 2019 at 08:22:09AM +0100, Clement Verna wrote: > Hi all, > > I would like to revert greenwave's gunicorn timeout to the default > 30s. Changing it to 10+min was useful for our investigation but it now > slows down bodhi cron job. Also the greenwave team is working on fix > for this so long term we should not need to have a specific timeout. > > I am leaving in place the longer OpenShift timeout on the route, so > that it is easier to know where the timeout comes from. > > diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml > b/roles/openshift-apps/greenwave/templates/buildconfig.yml > index d836b482d..7bb5420ba 100644 > --- a/roles/openshift-apps/greenwave/templates/buildconfig.yml > +++ b/roles/openshift-apps/greenwave/templates/buildconfig.yml > @@ -30,7 +30,6 @@ spec: > > # Become non-root again > USER 1001 > - ENTRYPOINT docker/install-ca.sh && gunicorn-3 --workers 8 > --timeout 660 --graceful-timeout 300 --bind 0.0.0.0:8080 > --access-logfile=- --enable-stdio-inheritance greenwave.wsgi:app > strategy: > type: Docker > dockerStrategy: Our investigation has shown that increasing the timeout does reduce the error rate. I am +1 to reducing it because 10 minutes is definitely way too big, but -1 to put it back to 30 seconds. Pierre _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
