https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
--- Comment #11 from Antoine hashar Musso has...@free.fr ---
When we migrated the beta cluster from pmtpa to eqiad, Sean Pringle added a
master / slave setup on beta. Apparently the slave is usually laggy.
It seems to be possible to make it
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
--- Comment #12 from Niklas Laxström niklas.laxst...@gmail.com ---
According to my latest knowledge the replication delay setting only exists in
recent MySQL [1] and not in MariaDB - unless the feature has been added
recently.
[1] I created a
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
--- Comment #13 from Antoine hashar Musso has...@free.fr ---
That might depends on the percona toolkit + some custom setup. I think
production has slaves which have a 24 hours delay.
Someone should talk about it with Sean Pringle.
--
You
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
--- Comment #15 from Sean Pringle sprin...@wikimedia.org ---
For comment #14:
[1]
https://git.wikimedia.org/blob/operations%2Fsoftware/ccbfe07353ce100bfe7d8557f9ceeeb28103d4be/dbtools%2Fevents_dbstore_delayed.sql#L64
--
You are receiving
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
--- Comment #14 from Sean Pringle sprin...@wikimedia.org ---
Production has slaves delayed by 24h using the MariaDB event scheduler [1] to
start/stop the replication threads. This is fine for a coarse lag values of a
few minutes, but inaccurate
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
Andre Klapper aklap...@wikimedia.org changed:
What|Removed |Added
See Also|
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
Nemo federicol...@tiscali.it changed:
What|Removed |Added
Keywords||ops, performance
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
Siebrand Mazeland s.mazel...@xs4all.nl changed:
What|Removed |Added
Blocks||1268
--
You
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
Faidon Liambotis fai...@wikimedia.org changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
--- Comment #9 from Niklas Laxström niklas.laxst...@gmail.com ---
Labs would be nice, but something that allows debugging and tweaking of the
code would be even nicer. I wonder if it would be possible to do this with
MediaWiki-Vagrant.
--
You
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
Siebrand Mazeland s.mazel...@xs4all.nl changed:
What|Removed |Added
Blocks||51731, 54579
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
Siebrand Mazeland s.mazel...@xs4all.nl changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
Niklas Laxström niklas.laxst...@gmail.com changed:
What|Removed |Added
Blocks||46716
--
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
--- Comment #7 from Krinkle krinklem...@gmail.com ---
Right, so if I understand you correctly, you're looking for an environment
where you can work on fixing bugs and testing bugfixes related to replication
lag.
In other words, a wiki (say,
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
--- Comment #6 from Niklas Laxström niklas.laxst...@gmail.com ---
I was more concerned about actually reproducing the issues reliably and having
possibility to debug them easily to understand the causes and to also to come
up and test fixes
https://bugzilla.wikimedia.org/show_bug.cgi?id=38945
Krinkle krinklem...@gmail.com changed:
What|Removed |Added
Summary|Way to simulate replication |Need a way to simulate
16 matches
Mail list logo
