If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Documenting dev database instances

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
5 years ago
3 years ago

People

(Reporter: selenamarie, Assigned: mpressman)

Tracking

Details

(Whiteboard: [2013q2])

In the documentation on mana, three databases are defined: 

DevDB
BackupDB
Development Database

The docs said that hosts are running on ports 4321, but currently on socorro1.dev we have: 

[postgres@socorro1 data]$ ps -ef | grep postmaster | grep -v grep
postgres  5624     1  0 Dec23 ?        00:00:00 /usr/pgsql-9.2/bin/postmaster -p 5499 -D /pgdata/pgslave/9.2/data
postgres 26592     1  0 Dec23 ?        00:00:11 /usr/pgsql-9.2/bin/postmaster -p 5432 -D /pgdata/crash-stats-dev/9.2/data

I assume that 'pgslave' is ReplayDB or BackupDB, and 'crash-stats-dev' is Development Database.

Looking into the directories, we have: 

[postgres@socorro1 ~]$ cd /pgdata/
[postgres@socorro1 pgdata]$ ls
9.0  crash-stats-dev  devdb  pgslave  tmp
[postgres@socorro1 pgdata]$ ls -lah
total 8.0K
drwxr-xr-x   7 root     root       74 Aug 27 14:18 .
dr-xr-xr-x. 26 root     root     4.0K Dec 23 01:18 ..
drwx------   3 postgres postgres   17 Jan 20  2012 9.0
drwx------   5 postgres postgres   40 Dec  9 12:35 crash-stats-dev
drwx------   5 postgres postgres   40 Nov 20 18:22 devdb
drwx------   7 postgres postgres  107 Dec  9 12:42 pgslave
drwxrwxrwx   3 root     postgres 4.0K Dec 23 14:39 tmp
[postgres@socorro1 pgdata]$ cd devdb
[postgres@socorro1 devdb]$ ls
9.0  9.2  archive
[postgres@socorro1 devdb]$ 
[postgres@socorro1 devdb]$ cd 9.2/
[postgres@socorro1 9.2]$ ls -tlr
total 0
drwx------ 2 postgres postgres 75 Dec  9 13:31 data
[postgres@socorro1 9.2]$ cd data
[postgres@socorro1 data]$ ls -tlr
total 32
-rw-r--r-- 1 root     root      4648 Dec  9 13:31 pg_hba.conf
-rw-r--r-- 1 postgres postgres   932 Dec  9 13:31 recovery.conf.disabled
-rw-r--r-- 1 postgres postgres 18010 Dec  9 13:31 postgresql.conf
[postgres@socorro1 data]$ 

Nothing is currently running out of 'devdb' directory. Should something be running in there?
I think Matt and I talked about this a while back; I think the dev database only needed 2 instances running on it, not 3. I think the 3rd instance was something Josh Berkus was using. If Matt can confirm, I can update the docs. Good catch!
Assignee: server-ops → mpressman
Summary: devdb instance on socorro1.dev is down → Documenting dev database instances
Here are some pages to double-check the info on:
https://mana.mozilla.org/wiki/display/websites/Updating+Staging+and+Dev+Snapshots+of+Postgres+Database

https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=5734601

https://mana.mozilla.org/wiki/display/SYSADMIN/Databases#Databases-Postgres

Let's make this a q2 goal to make sure the information is up-to-date and accurate on those three pages, and if there's duplicate information it's OK to link between the pages.
Whiteboard: [2013q2]
Depends on: 856164
This will be done by the end of the week (Fri 12 July).
(Assignee)

Comment 4

4 years ago
https://mana.mozilla.org/wiki/display/SYSADMIN/Databases#Databases-Postgres
Updated to show that only the partial breakpad database on the primary 5432 port is on host
(Assignee)

Comment 5

4 years ago
https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=5734601
Updated Development Databases section. Removed reference to ReplayDB and changed the backup location to backup4.db.phx1
(Assignee)

Comment 6

4 years ago
https://mana.mozilla.org/wiki/display/websites/Updating+Staging+and+Dev+Snapshots+of+Postgres+Database
Removed references to ReplayDB and DevDB instances in manual update procedure

With the removal of the DevDB instance, the process is much shorter and simpler to run manually
Status: NEW → RESOLVED
Last Resolved: 4 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.