Change Details

Followup to T306602: > Sadly, in-place migration is only possible up to 20221024183507.0.0 version. After that, [[ https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html | there is a format migration that requires full reimport of all files ]] 🤨, and that won't be trivial or fast. At that point, I would consider alternative storage engines, given the effort to migrate away would be about the same and one of the original reasons to use it was its simplistic storage format (nice for backups). Consider what's the best way to move forward- some quick alternatives: * Keep the current version until migration is needed due to hw refresh - reimport then * Make a resource intensive (both human and disk) migration to the new format * Migrate away to a new solution * Setup some custom or 3rd pary software "`S3` to filesystem" proxy to keep the service working without needing a file migration This needs deep discussion and research and balancing of the different options

Followup to T306602: > Sadly, in-place migration is only possible up to 20221024183507.0.0 version. After that, [[ https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html | there is a format migration that requires full reimport of all files ]] 🤨, and that won't be trivial or fast. At that point, I would consider alternative storage engines, given the effort to migrate away would be about the same and one of the original reasons to use it was its simplistic storage format (nice for backups). Consider what's the best way to move forward- some quick alternatives: * Keep the current version until migration is needed due to hw refresh - reimport then * Make a resource intensive (both human and disk) migration to the new format * Migrate away to a new solution * Setup some custom or 3rd pary software "`S3` to filesystem" proxy to keep the service working without needing a file migration - reevaluate at hw refresh time This needs deep discussion and research and balancing of the different options

Followup to T306602: > Sadly, in-place migration is only possible up to 20221024183507.0.0 version. After that, [[ https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html | there is a format migration that requires full reimport of all files ]] 🤨, and that won't be trivial or fast. At that point, I would consider alternative storage engines, given the effort to migrate away would be about the same and one of the original reasons to use it was its simplistic storage format (nice for backups). Consider what's the best way to move forward- some quick alternatives: * Keep the current version until migration is needed due to hw refresh - reimport then * Make a resource intensive (both human and disk) migration to the new format * Migrate away to a new solution * Setup some custom or 3rd pary software "`S3` to filesystem" proxy to keep the service working without needing a file migration - reevaluate at hw refresh time This needs deep discussion and research and balancing of the different options