On Fri, 2019-03-15 at 12:11 +0100, Clement Verna wrote: > I would like to increase this timeout to 330 seconds, greenwave will > timeout after 300 seconds. I don't think we should do this. Two problems immediately come to mind. Bodhi still gets timeout errors from Greenwave, because Bodhi will not wait forever for a response. Now instead of 500 error e-mails from Greenwave, I get just as many timeout error e-mails. Secondly, there are currently 1,717 updates in the testing status in Bodhi. This means that Bodhi's cron job will make that many queries each time it runs. We do want to limit how much time Greenwave can take to respond, otherwise we will just pile up cron jobs. This change effectively made Bodhi's cron job slower, but did not lower the error rate.
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 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
