This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19274 - Investigate possible database problem
Summary: Investigate possible database problem
Status: RESOLVED FIXED
Alias: None
Product: webplatform.org
Classification: Unclassified
Component: infrastructure (show other bugs)
Version: unspecified
Hardware: PC All
: P1 critical
Target Milestone: ---
Assignee: Doug Schepers
QA Contact: public-webplatform-bugs list
URL:
Whiteboard:
Keywords:
: 19263 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-10-04 10:58 UTC by Doug Schepers
Modified: 2012-10-05 04:37 UTC (History)
3 users (show)

See Also:


Attachments

Description Doug Schepers 2012-10-04 10:58:24 UTC
Chris Mills reported: 
[[
Can anyone tell me what happened to the CSS tutorials page and main yesterday?

http://docs.webplatform.org/wiki/CSS/tutorials

The page linked from the main page seems to have been changed to 

http://docs.webplatform.org/test/CSS/tutorials

And loads of the links to CSS articles I added to the page seem to have been removed.

and the main page (http://docs.webplatform.org/wiki/Meta:Main_Page) structure has been changed again.

...

It is weird as when I check the history on those pages, it says the last person to make changes was me. But this can't be, as there is definitely stuff I put up there yesterday/the day before that has been removed again.
]]

Karl Dubost replied:
[[
I have seen db issues yesterday. So I wonder if it's related to a master slave interaction.
]]
Comment 1 Ryan Lane 2012-10-04 19:10:03 UTC
I added a database replica and changed MediaWiki's configuration to
use a slave for reads and a master for writes. MediaWiki's
configuration for this uses a different variable; so we went from:

http://www.mediawiki.org/wiki/Manual:$wgDBserver

to:

http://www.mediawiki.org/wiki/Manual:$wgDBservers

Apparently, MediaWiki uses $wgDBserver for some other magical
settings. One of which is the default for:

http://www.mediawiki.org/wiki/Manual:$wgCachePrefix

With no prefix for the memcache keys, both test and current were
clobbering each other's keys, including the parser cache entries.

I've fixed this by explicitly setting the cache prefix, and I've also
added $wgDBserver back in, in case it was used for other magical
purposes.
Comment 2 Scott Sweeney 2012-10-05 04:37:12 UTC
*** Bug 19263 has been marked as a duplicate of this bug. ***