| daniel added a comment. |
My 2ยข
@jcrespo wrote
If these create light-weight queries only, lets disconnect and connect after some amount of seconds.
Teaching LoadBalance to throw away connections after a minute or so would be easy. But would that be sufficient? Reconnecting would use the old configuration that was valid when the process started. Reconfiguring on the fly is a lot more tricky.
If dump hosts are too slow, let's give them better resources.
Yes, please. When dump scripts run for weeks instead of days, they tend to fail at some point. I agree that we shouldn't hit the web-facing databases for making dumps. But if that means we get no dumps at all, that's not good either...
If there is a problem with the connection framework, let'x fix it with the addition of a proxy/persistent connections manager.
My impression is that what we want here is the opposite of persistent connections. Making it possible to re-configure MediaWiki mid-air would certainly be nice, it's something I have been working on with respect to dependency injection and unit testing.
Cc: daniel, hoo, ArielGlenn, jcrespo, Zppix, D3r1ck01, Izno, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
