Issue Details (XML | Word | Printable)

Key: MBS-3156
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Normal Normal
Assignee: Ian McEwen
Reporter: Nicholas J Humfrey
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
MusicBrainz Server

Slaves should use the READONLY database settings from DBDefs.pm

Created: 03/Aug/11 03:44 PM   Updated: 09/Jul/12 07:30 AM   Resolved: 09/Jul/12 07:30 AM
Component/s: Admin
Affects Version/s: None
Fix Version/s: Bug fixes, 2012-07-09


 Description  « Hide

By configuring slave instances to use the READONLY database settings from DBDefs.pm it will allow easier scaling of MusicBrainz to use clusters of read-only Postgres slaves.

The cron update scripts will continue to use the READWRITE database settings, which would be the local Postgres master server.



Sort Order: Ascending order - Click to sort in descending order
Ian McEwen added a comment - 20/Apr/12 11:41 AM

As far as I know this is how slaves work already. Is this ticket valid?


Oliver Charles added a comment - 20/Apr/12 12:25 PM - edited

Yes, it's still valid - the READONLY option is completely unused.


Oliver Charles added a comment - 20/Apr/12 12:25 PM
ollie@deimos ~/Work/MusicBrainz/mb_server (mbs-3788*) % ack 'READONLY' lib
lib/DBDefs.pm
68:    # READONLY => undef,

lib/DBDefs.pm.default
55:    # READONLY => undef,

Ian McEwen added a comment - 25/Jun/12 09:54 PM

Ian McEwen added a comment - 26/Jun/12 05:14 PM

I did this incorrectly, needs more work – hopefully update soon.