Specifically:
if we measure read only time as "an editor can't start an edit because
wikis are read only", then the read-only time is 119s;
if we measure it by the last timestamp of an edit being saved, that's 94
seconds.
As Amir explained, we leave some room for propagation of the MediaWiki
The Search Platform team office hour is happening 1 hour from now.
See you there!
Guillaume
On Fri, 24 Feb 2023 at 17:04, Guillaume Lederrey
wrote:
> Hello all!
>
> The Search Platform Team usually holds an open meeting on the first
> Wednesday of each month. Come talk to us about anything
Dear Wikitechians,
Dear colleagues,
The switchover process requires a *brief read-only period for all
Foundation-hosted wikis*, which started at *14:00 UTC on Wednesday March
1st*, and lasted *119 seconds*. All our public and private wikis continued
to be available for reading as usual. Users
Clément Goubert and everybody,
I analyzed https://stream.wikimedia.org/v2/stream/recentchange and i
have the another results.
Last change (before migration): 2023-03-01T14:00:30
First change (after migration):2023-03-01T14:02:05
Result: Down time (14:00:31 to 14:02:05) is 94s.
I think that
It's a bit complicated.
When SRE sets the read-only mark, they start counting from that time and it
starts propagating which takes a while to be actually shown to all users
but some users might still see the RO error while some actual writes are
happening somewhere else because the cache is not
Hello.
Is the new files bug happening because of the database switch? And if it
is, do you fix it?
The story: If you reupload file, local or on commons, the new version does
not create thumb, and the old one is shown in articles. The only way to see
a new version is opening the file in media:
I see. Very well, I'll open a task.
Thank you.
Igal
בתאריך יום ד׳, 1 במרץ 2023, 22:07, מאת Brian Wolff :
> You should probably just file a bug.
>
> Its certainly plausible it had something to do with data center switch,
> but it could just as equally be unrelated. It requires someone to
>
You should probably just file a bug.
Its certainly plausible it had something to do with data center switch, but
it could just as equally be unrelated. It requires someone to investigate
what part of the system failed (job queue? Varnish? Swift?) which would
then lead to a root cause. Its pretty
Le 28/02/2023 à 21:42, MusikAnimal a écrit :
Hello! Where might I find documentation on the new maintenance runner
system? I can't find any examples in the Phabricator task or the
linked RFC, and searching for "MaintenanceRunner" or "run.php" yields
no results on mediawiki.org
