https://bugzilla.wikimedia.org/show_bug.cgi?id=48025
Web browser: ---
Bug ID: 48025
Summary: Zuul is ultra slow post Jenkins upgrade
Product: Wikimedia
Version: wmf-deployment
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: Unprioritized
Component: Continuous integration
Assignee: wikibugs-l@lists.wikimedia.org
Reporter: has...@free.fr
CC: has...@free.fr, innocentkil...@gmail.com,
krinklem...@gmail.com
Classification: Unclassified
Mobile Platform: ---
Jenkins was slow to restart (bug 47120) and got upgraded. Since them Zuul has
been very slow to trigger the build.
After investigating with upstream (James E. Blair from OpenStack), it turns out
Zuul wait for the results of JSON API calls which are meant to verify whether a
job exist before triggering it.
We have found a few API calls that took 2 to 4 minutes which would lock Zuul
internal scheduler. In the end, it would be spending most of its time waiting.
This is a major issue.
A workaround is to skip the API call. James advised to fake the ExtendedJenkins
class in Zuul to pretends jobs always exist.
https://gerrit.wikimedia.org/r/#/c/62095/
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
