Page MenuHomePhabricator

Convert Phacility file storage to use S3
Closed, ResolvedPublic


We're using MySQL storage in Phacility right now; we should switch instances to use S3

Event Timeline

epriestley raised the priority of this task from to Needs Triage.
epriestley updated the task description. (Show Details)
epriestley added a project: Phacility.
epriestley moved this task to Backlog on the Phacility board.
epriestley added a subscriber: epriestley.

We should really use IAM Roles for this since putting root API keys on instances seems Very Questionable.

btrahan triaged this task as Normal priority.Feb 17 2015, 10:51 PM
epriestley raised the priority of this task from Normal to High.Jan 9 2016, 11:47 AM
epriestley added a project: Files.

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.

The second biggest source of storage pressure appears to be test instances that, e.g., imported the Linux Kernel and were then suspended. I've filed T10166 to follow up.

epriestley claimed this task.

After rCORE538a9808, all new files larger than 64KB go to S3.