Last Comment Bug 477099 - Ensure mysql slaves are locked to read-only mode
: Ensure mysql slaves are locked to read-only mode
Product: Graveyard
Classification: Graveyard
Component: Server Operations (show other bugs)
: other
: All Other
-- minor (vote)
: ---
Assigned To: Dave Miller [:justdave] (
: matthew zeier [:mrz]
Depends on:
  Show dependency treegraph
Reported: 2009-02-05 12:07 PST by Dave Miller [:justdave] (
Modified: 2015-03-12 08:17 PDT (History)
0 users
mzeier: needs‑downtime+
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Dave Miller [:justdave] ( 2009-02-05 12:07:16 PST
The slave databases are supposed to be locked via configuration to be read-only, so that it's not possible to write to them except via replication.  I've recently discovered that some of them aren't, and this can cause problems with applications that misbehave and write to the wrong DB handle, causing slaves to be out-of-sync, and we'd never know there was a problem because no error would be generated until some day maybe a write to the master hits a duplicate key or something.
Comment 1 User image matthew zeier [:mrz] 2009-02-17 13:21:14 PST
I think this is on for tonight - start time, downtime estimate?
Comment 2 User image Dave Miller [:justdave] ( 2009-02-17 13:27:31 PST
7pm pacific, no downtime expected, it's a runtime change.  Just announcing it so people know to file bugs if they notice anything funny after it's been done.
Comment 3 User image Dave Miller [:justdave] ( 2009-02-17 20:16:23 PST

Note You need to log in before you can comment on or make changes to this bug.