We should look at moving the analytics databases off of this cluster. At present this would free up nearly 700GB of the 1.6GB total.
We have frdb1003 already for fundraising analytics. Can we move these databases there?
Another question is how far are we from being able to phase out faulkner, pgehres, and fredge databases entirely, and move their functionality to grafana and Superset?
faulkner - This should be an easy one, it is a static legacy pre-2013 analytics database. It's probably no longer used all, but we need to confirm. [Decision: remove from fundraisingdb cluster, leave on frdb-analytics for now. T256670]
pgehres - This is an active analytics database that is populated from the kafkatee banner/landing page pipelines. Data is imported on 15 minute intervals by process-control jobs on civi1001. We could simply move the database, but we should also consider moving the jobs that populate it to fran1001 to take load off of civi1001. DjangoBannerStats uses separate database handles to make connections to pgehres, civicrm, and drupal databases, configured in /etc/django_settings.py. [Decision: migrate to fr-analytics cluster. T258526]
fredge - As noted in comments below, this is queried against the civicrm database and may not be something we can move. [Decision: can't move at this time]