Closed Bug 646857 Opened 14 years ago Closed 14 years ago

Configure MarkUP to send database reads and writes to different database servers

Categories

(Websites Graveyard :: markup.mozilla.org, defect)

Product:
Websites Graveyard
Component:
markup.mozilla.org
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: lmesa, Assigned: adam)

Details

(Whiteboard: [qa-])

Please configure MarkUP to send database reads and writes to different database servers.
you want to use the django-multidb-router library for this.
This has been updated + committed.
Looks like there was in the above linked commit as well as this one: https://github.com/mozilla/markup/commit/24b766bfe31b6524163e80030f9bf73e4cf46841
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Is this a [qa-] or is this already being employed on stage and we'd experience the app misbehaving if there was a defect?
(In reply to comment #6) > Is this a [qa-] or is this already being employed on stage and we'd experience > the app misbehaving if there was a defect? The app seems to be configured to use a master and slave DB on stage.
A next question ... can we cause a series of "failures" to test that fail-over is occurring as expected?
What failures do you want to test? DB writes go to the master and reads hit the slave. If the DB can't be written to, the site should be read only. If you have test cases, I might be able to firewall either database for you to test. This will be fairly short-lived, since the stage server has other projects that need to connect to the same DB servers.
Great! Let me check-in with the group at our meeting today to assess the validity of the testcases.
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [qa-]
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.