| jcrespo added a comment. |
Let me show you the weight of these servers:
's5' => array( 'vslow' => array( 'db1045' => 1, ), 'dump' => array( 'db1045' => 1, ), 'api' => array( 'db1070' => 1, 'db1071' => 1, ), 'watchlist' => array( 'db1026' => 1, ), 'recentchanges' => array( 'db1026' => 1, ), 'recentchangeslinked' => array( 'db1026' => 1, ), 'contributions' => array( 'db1026' => 1, ), 'logpager' => array( 'db1026' => 1, ), ),
Do you see db1071 anywhere? Not on dump, not on vslow (and I just added it to api, it was not there before, when the issue started happening). So yes, I only expect most short-lived connections (the ones created by non-api end-user requests) to only go to the new servers while they are being tested. This separation is important due to performance and HA reasons. By not following mediawiki standards you are threatening the reliability of the site, for wikidatawiki and for dewiki users (which are already not happy).
There is not need to change any mediawiki architecture. terbium jobs must use the 'vslow' role. If you think only one server is not enough, please say so and we change the config to add more servers to vslow (which we certainly can do now that we have more servers), but not violate mediawiki contract of roles sending long-running connections to servers that are not ready for them.
The same thing applies for dumps- if more are needed, configuration is changed, not hardcoding the wrong ones.
These changes literally only need on parameter change loadbalancer->get(SLAVE, 'dump')
Cc: daniel, hoo, ArielGlenn, jcrespo, Zppix, D3r1ck01, Izno, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
