- User Since
- Oct 20 2014, 5:17 PM (348 w, 6 h)
- LDAP User
- MediaWiki User
Nov 2 2018
Oct 30 2016
Sep 23 2016
Apr 28 2016
Dec 24 2015
Dec 6 2015
Jul 23 2015
I believe it was semi arbitrary and based on budget. We have 15 nice
machines in the eqiad cluster and 16 good machines and I guestimated that
half again as many would be enough but never ran any hard numbers. 24 may
be too many but it doesn't feel like too too many. If it is too few we can
lower the rescore window for phrases on queries sent to that cluster to
lower the load.
Jul 22 2015
Jul 21 2015
Ahk! I just finished this! I ran the Cirrus test suite with these instructions:
Jul 20 2015
As Chad said this is working as designed. We should throw these errors into the cirrus log rather than the general hhvm warning log though.
Jul 17 2015
I think this is as simple as https://gerrit.wikimedia.org/r/#/c/225483/
This issue is so amazingly amazing I think I'd like to steal it.
Cool. Then the jdk upgrade can hit the machines any time. We can do it when
we're logged in for the the rolling restart or you can. Or puppet can if we
use puppet for that sort of thing.