Hi,
We're about to apply necessary schema changes for Wikimedia's MediaWiki 1.17 upgrade to the Toolserver databases. We will apply the changes to one server for each cluster at once; while the primary server is being updated, user databases will be unavailable, but replication won't be interrupted.
The exception is s2/s5, which currently only has one server. Databases on these clusters will not be replicated and might be partially unavailable during the maintenance.
This was not announced in advance since we only learnt about the changes about 10 minutes ago. Sorry.
- river.
On Mon, Feb 7, 2011 at 7:43 AM, River Tarnell river@yvaine.tcx.org.uk wrote:
This was not announced in advance since we only learnt about the changes about 10 minutes ago. Sorry.
Is this something we can do about in the future? If somebody notices that WMF is planning schema changes or master switches or cluster splits should they file a JIRA ticket, or poke you on IRC or something?
Bryan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Bryan Tong Minh:
On Mon, Feb 7, 2011 at 7:43 AM, River Tarnell river@yvaine.tcx.org.uk wrote:
This was not announced in advance since we only learnt about the changes about 10 minutes ago. Sorry.
Is this something we can do about in the future?
I've asked WMF (i.e., Tim) to let us know about schema changes in advance next time, so we can apply them with less service interruption.
- river.
River Tarnell river.tarnell@wikimedia.de wrote:
This was not announced in advance since we only learnt about the changes about 10 minutes ago. Sorry.
Is this something we can do about in the future?
I've asked WMF (i.e., Tim) to let us know about schema changes in advance next time, so we can apply them with less service interruption.
Given WMDE's recent fundraising changes which now allow sup- porting WMF directly, are there any plans to blur the clear distinction between WMF's farm and the Toolserver database servers with the accompanying headaches in the near future?
Tim
In article m339nzkg9a.fsf@passepartout.tim-landscheidt.de, Tim Landscheidt tim@tim-landscheidt.de wrote:
Given WMDE's recent fundraising changes which now allow sup- porting WMF directly, are there any plans to blur the clear distinction between WMF's farm and the Toolserver database servers with the accompanying headaches in the near future?
Not that I know of. What sort of changes were you expecting?
- river.
River Tarnell r.tarnell@IEEE.ORG wrote:
Given WMDE's recent fundraising changes which now allow sup- porting WMF directly, are there any plans to blur the clear distinction between WMF's farm and the Toolserver database servers with the accompanying headaches in the near future?
Not that I know of. What sort of changes were you expecting?
I was expecting nothing :-). But as the Toolserver was miss- ing on WMF's radar in the past several times, one obvious solution would be to treat the Toolserver database servers as part of WMF's domain so they can use their SOPs (*1) to maintain them instead of manually coordinating with the Toolserver admins (or not).
Tim
(*1) With a twist for the user databases/access restric- tions, of course.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
In article m3hbcesjx1.fsf@passepartout.tim-landscheidt.de, Tim Landscheidt tim@tim-landscheidt.de wrote:
one obvious solution would be to treat the Toolserver database servers as part of WMF's domain so they can use their SOPs (*1) to maintain them instead of manually coordinating with the Toolserver admins (or not).
I don't think that would be any easier. Our database systems are completely different from theirs, so it would require all WMF admins to learn (and remember) a new procedure before they could change anything on their side. Since they usually don't think to notify us of major changes in advance, I don't think they would be very happy with that.
- river.
toolserver-l@lists.wikimedia.org