The log processor currently runs on civi1001 and the database (pgehres) on frdb1002 replicating to the rest of the fundraisingdb cluster. We should be able to move these to fran1001/frdb1003 and reduce demands on donation processing systems. This has been discussed on T255456.
Description
Description
Details
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T241083 Epic: fundraising database scalability | |||
Resolved | Jgreen | T258526 Migrate DjangoBannerStats processing and database to fundraising analytics cluster | |||
Resolved | Pcoombe | T258600 reconfigure 'statler' to use fundraising analytics database (frdb1003) instead of frdev1001 |
Event Timeline
Comment Actions
- configured nfs mount fran1001 -> frban1001 for access to impression logs
- disabled 'pgehres' database replication to frdb1003
- installed DjangoBannerStats and process-control on fran1001
- configured DjangoBannerStats on fran1001 to update frdb1003/pgehres database
- enabled fran1001 process-control job banner_impressions_loader
Comment Actions
Change 620725 had a related patch set uploaded (by Jgreen; owner: Jgreen):
[operations/puppet@production] nsca_frack.cfg.erb - remove check_ipsec from civicrm servers, add to fran1001
Comment Actions
Change 620725 merged by Jgreen:
[operations/puppet@production] nsca_frack.cfg.erb - remove check_ipsec from civicrm servers, add to fran1001
Comment Actions
- process-control banner log update job removed from civi1001
- DjangoBannerStats code removed from civi1001
- frdeploy configured not to deploy DjangoBannerStats to civi1001
- nfs and ipsec configuration removed from civi*
- iptables policy updated and refreshed on all hosts
- database dropped from frdb1002 and replicas
- database permissions removed from frdb1002 and replicas