Open Stack

On 12/08/12 20:22, Robert Collins wrote:

> So - do we have a backfiller around, to do this with minimal
> (subsecond) downtime in stages, or do we just bite the bullet and
> accept that the migration will take as long as it takes? Its a very
> narrow table, and I'd expect even pretty large sites to be looking at
> no more than 10-20 seconds to perform the migration.

The nova answer to this would be to just put in a database migration and
suck up the slowness. I guess its assumed that operators are performing
those migrations during downtime windows.

You should add the indexes while you're at it...

Mikal