We're using MySQL storage in Phacility right now; we should switch instances to use S3
Revisions and Commits
- Mentioned In
- T10236: Enable `innodb_file_per_table` and migrate existing databases in the cluster
T10114: Upgrading: Amazon S3 Configuration Changes
T7148: Allow users to export their data from Phacility
- Mentioned Here
- T10166: Build a permanent destruction workflow for Phacility instances
T5155: Evaluate support for AWS IAM Roles in S3 Client
Some of the older instances are beginning to collect enough data in MySQL to motivate this more strongly in the near term, especially as database data is currently stored multiple times on disk in backups.
We should be in good shape to move forward here after changes in T5155. My plan is roughly:
- deploy the new stuff here for a bit;
- then, start doing new writes to S3 in the cluster;
- then, migrate older data off some of the bigger instances.
I'll probably do the actual migration stuff next weekend. We aren't facing any urgent pressure here, but are down to maybe ~2-ish months of headroom.
This is now available in the cluster, but the storage engine currently never selects it for new writes because MySQL is still configured to allow 8MB chunks. I'm going to selectively migrate some data, but probably not turn default writes on for a week or so.