812036 - set up Sentry MySQL DB nodes in PHX1

Status: RESOLVED FIXED

(Data & BI Services Team :: DB: MySQL, task)

Description

[Jake Maul [:jakem]]

These nodes are puppetized and ready for some DBA lovin'. :)

sentry1.db.phx1.mozilla.com
sentry2.db.phx1.mozilla.com

Straightforward MySQL cluster. Need Zeus VIP for rw, but at present no need for ro (app doesn't seem to support ro slaves). The load is likely to be insert-heavy, as Sentry is a collector for errors/tracebacks from web apps... new errors are likely to arrive individually, and then reported on in bulk via the web interface.

Thanks!

Comment 1

[Jake Maul [:jakem]]

I think all Zeus work is done. I will open a separate bug to have netflows created.

I have reserved/allocated/assigned VIPs for this (rw and ro, since I was there anyway):

10.8.70.159 - sentry-zlb-rw.db.phx1.mozilla.com.
10.8.70.160 - sentry-zlb-ro.db.phx1.mozilla.com.

Forward and Reverse DNS is done.

Zeus Traffic IP Groups created. Ping confirms success.

Zeus Pools "db-sentry-rw" and "db-sentry-ro" configured. I just mirrored the config for "db-plugins-r[wo]" for this... it seemed to be a reasonable choice for how to make a 2-node cluster. sentry1.db.phx1 is currently the active rw server, and sentry2.db.phx1 is the active ro server. The rw pool has a failover pool set- fails over to the ro pool.

Zeus Virtual Servers "db-sentry-rw" and "db-sentry-ro" configured. Again mirroring "db-plugins-r[wo]".

Health checks are all failed right now, due to MySQL not being actually set up... I'm looking at puppet and I think I could make it go, but would rather have someone more familiar with how our MySQL / puppet configs work do it. :)

Comment 2

[Jake Maul [:jakem]]

This is all done except for backups, and there's a separate bug opened for that. Thanks!