setup postgres replication for breakpad in staging.

RESOLVED FIXED

Status

--
minor
RESOLVED FIXED
10 years ago
4 years ago

People

(Reporter: aravind, Assigned: chizu)

Tracking

Details

(Reporter)

Description

10 years ago
Please setup postgres replication for breakpad in the staging environment.  The staging db lives on tm-stage01-master01.  The purpose of this replicated environment is to be able to make backups of the db from the slave without impacting the production db performance.  Once the staging env is setup and work, we can then deploy this to production.
(Reporter)

Updated

10 years ago
Assignee: server-ops → thardcastle
(Reporter)

Updated

10 years ago
Blocks: 469220
(Reporter)

Updated

10 years ago
Blocks: 468465
No longer blocks: 469220
(Assignee)

Comment 1

10 years ago
My plan for this is shipping completed write ahead logs to a slave. The slave will replay the logs regularly and we'll backup the write ahead logs and the slave state.

I'll be deploying and verifying this on stage in the next couple days.

Comment 2

10 years ago
chizu, for scheduling/planning, do you have an ETA on this?
(Assignee)

Comment 3

10 years ago
This just needs an ACL from tm-stage01-master01 to dracula, the rest is ready.
(Assignee)

Comment 4

10 years ago
This is replicating and I've made and restored backups from it. It just needs some more polish and documentation before I can call this done.
Status: NEW → ASSIGNED
Great news, Trevor!  Thanks for picking this up. <3
(Assignee)

Comment 6

10 years ago
I should note how this is a different than MySQL replication. The master keeps write ahead logs normally. To make a slave we checkpoint one, rsync the database directory over to the slave, and put the slave into recovery mode pulling in those logs over nfs or rsync. Because the slave is in recovery mode, it's not serving queries. This makes it great for backups and failover in case the master dies, but it can't take read-only queries while replicating. Recovery mode can be stopped to run queries in batches.
(Assignee)

Comment 7

10 years ago
Documented and running.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.