OVHcloud Web Hosting Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
Legacy CloudDB, sql021
Scheduled Maintenance
Report for Web Cloud
Completed
Sur de vieilles instances MySQL CloudDB WebHosting, nous avons constaté des mises à jour en erreur au moment du passage de MySQL 5.7 à 8.0.
Les instances concernées sont relativement peu nombreuses. Il s'agit d'instances:
- Créées avant 2017
- et portant un nom préfixé par «sqlprive-»
- et hébergées sur le cluster sql021
- et contenant des tables InnoDB ayant été créées sur une version de MySQL strictement inférieure à 5.5 (MyISAM étant à l'époque le format par défaut)
- et utilisant le format de fichier InnoDB \"Antelope\"
Ces erreurs sont dues à un vieux format de fichier Antelope qui n'est plus supporté en version 8.0. Attention, sur MySQL 8.0, le format Antelope est toujours supporté, même si c'est la première version de MySQL où il n'est plus possible de créer des tables avec ce format. Ce qui n'est plus supporté, ce sont les tables Antelopes créées dans une version strictement inférieure à MySQL 5.5.
Afin de corriger durablement ce problème et vous permettre de migrer vers MySQL 8.0, nous allons migrer toutes les tables des CloudDB MySQL ayant un format de fichier Antelope pour les passer en Barracuda. Les autres tables (MyISAM ou InnoDB Barracuda) resteront inchangées. Un dump des bases concernées sera fait juste avant la migration. Vous retrouverez ces dumps dans votre Control Panel, à côté des autres dumps quotidiens.
Ces migrations seront faites mardi 2021-04-20, mercredi 2021-04-21, lundi 2021-04-26 et mardi 2021-04-27. Aucune coupure n'est à prévoir, juste un lock des tables allant de quelques dixièmes de secondes pour les tables les plus petites, à quelques minutes pour les plus grosses.
---
On very old MySQL CloudDB WebHosting instances, we noticed failing upgrades when moving from MySQL 5.7 to 8.0.
Impacted instances are relatively few. These are instances:
- Created before 2017
- and prefixed with \"sqlprive-\"
- and hosted on the sql021 cluster
- and having InnoDB tables created on a MySQL version strictly less than 5.5 (MyISAM was the default format then)
- and using the InnoDB file format \"Antelope\"
Those errors are due to an old Antelope file format that is no more supported in the 8.0 version. Warning, on MySQL 8.0, the Antelope format is still supported, even if this is the first version where you can not create tables using that
format. What is no more supported are the Antelope tables created in a version striclty less than MySQL 5.5.
To sustainably fix this issue and allow you to migrate to MySQL 8.0, we will migrate all the CloudDB MySQL tables having an Antelope file format to move them to Barracuda. The other tables (MyISAM or InnoDB Barracuda) will be kept unchanged. A dump of the concerned databases will be done just before the migration. You'll find those dumps in your Control Panel, next to the other daily dumps.
Those migrations will be done on Tuesday 2021-04-20, Wednesday 2021-04-21, Monday 2021-04-26 and Tuesday 2021-04-27. No downtime, only table locks during few millisecs for the smallest tables to a few minutes for the biggest ones.
Update(s):
Date: 2021-04-29 15:17:14 UTC
Intervention completed successfully on all the MySQL 5.5 of the sql021 cluster.
Another Travaux Task will be opened for the MySQL 5.6 and 5.7 parts.
Date: 2021-04-29 14:48:29 UTC
clouddb031.sql021: 100%
clouddb032.sql021: 100%
clouddb036.sql021: 98%
clouddb038.sql021: 100%
clouddb039.sql021: 100%
clouddb041.sql021: 94%
clouddb043.sql021: 71%
Date: 2021-04-29 13:25:37 UTC
The intervention is continuing on the host that had not been completed yesterday…
Date: 2021-04-28 20:17:49 UTC
clouddb030.sql021: 100%
clouddb031.sql021: 83%
clouddb032.sql021: 67%
clouddb033.sql021: 100%
clouddb035.sql021: 100%
clouddb036.sql021: 40%
clouddb038.sql021: 86%
clouddb039.sql021: 93%
clouddb041.sql021: 42%
clouddb042.sql021: 100%
clouddb043.sql021: 13%
Intervention will continue tomorrow.
Date: 2021-04-28 16:30:30 UTC
intervention is continuing on the host that had not been completed yesterday + on clouddb04[1-3].sql021.
Date: 2021-04-27 21:19:01 UTC
clouddb029.sql021: 100%
clouddb030.sql021: 74%
clouddb031.sql021: 64%
clouddb032.sql021: 67%
clouddb033.sql021: 94%
clouddb034.sql021: 100%
clouddb035.sql021: 40%
clouddb036.sql021: 15%
clouddb037.sql021: 100%
clouddb038.sql021: 86%
clouddb039.sql021: 65%
clouddb040.sql021: 100%
Intervention will continue tomorrow.
Date: 2021-04-27 20:25:39 UTC
clouddb029.sql021 and clouddb03[0-6].sql021: still ongoing…
clouddb03[7-9].sql021 and clouddb040.sql021: starting…
Date: 2021-04-27 19:42:11 UTC
clouddb02[5-8].sql021: done
clouddb0{29,30,31,32}.sql021: still ongoing…
clouddb03[3-6].sql021: starting…
Date: 2021-04-27 18:37:17 UTC
clouddb02{0,2,3,4}.sql021: done
clouddb02[5-8].sql021: still ongoing…
clouddb0{29,30,31,32}.sql021: starting…
Date: 2021-04-27 15:57:40 UTC
The intervention is continuing on clouddb02{0,2,3,4}.sql021 and starting on clouddb02[5-8].sql021…
Date: 2021-04-26 22:33:45 UTC
clouddb018.sql021: 100%
clouddb019.sql021: 100%
clouddb020.sql021: 51%, will be completed tomorrow
clouddb021.sql021: 100%
clouddb022.sql021: 62%, will be completed tomorrow
clouddb023.sql021: 95%, will be completed tomorrow
clouddb024.sql021: 60%, will be completed tomorrow
Date: 2021-04-26 21:04:06 UTC
clouddb012.sql021: 100%
clouddb015.sql021: 100%
clouddb016.sql021: 100%
clouddb017.sql021: 100%
clouddb018.sql021: 63%
clouddb019.sql021: 80%
clouddb020.sql021: 14%
clouddb021.sql021: 41%
clouddb022.sql021: 11%
clouddb023.sql021: 12%
clouddb024.sql021: 17%
Date: 2021-04-26 20:35:28 UTC
clouddb012.sql021: 93%
clouddb015.sql021: 70%
clouddb016.sql021: 91%
clouddb017.sql021: 68%
clouddb018.sql021: 36%
clouddb019.sql021: 67%
clouddb02[0-4].sql021: starting…
Date: 2021-04-26 20:01:43 UTC
clouddb012.sql021: 54%
clouddb015.sql021: 30%
clouddb016.sql021: 64%
clouddb017.sql021: 36%
clouddb018.sql021: 06%
clouddb019.sql021: 25%
Date: 2021-04-26 19:01:31 UTC
clouddb011.sql021: 100%
clouddb012.sql021: 35%
clouddb013.sql021: 100%
clouddb014.sql021: 100%
clouddb015.sql021: 27%
clouddb016.sql021: 60%
clouddb01[7-9].sql021: starting…
Date: 2021-04-26 17:14:04 UTC
clouddb010.sql021: 100%
clouddb011.sql021: 60%
clouddb012.sql021: 26%
clouddb013.sql021: 72%
clouddb014.sql021: 71%
clouddb01{5,6}.sql021: starting…
Date: 2021-04-26 16:32:56 UTC
clouddb010.sql021: 54%
clouddb011.sql021: 17%
clouddb012.sql021: 17%
clouddb013.sql021: 19%
clouddb014.sql021: 22%
Date: 2021-04-26 15:56:42 UTC
The intervention is starting on clouddb01{0-4}.sql021, on MySQL 5.5 instance only for now…
Date: 2021-04-21 20:34:45 UTC
Intervention completed successfully. All the MySQL 5.5 instances are OK on clouddb00[1-9].sql021.
Next intervention on Monday 2021-04-26.
Date: 2021-04-21 20:10:01 UTC
Intervention completed, except on clouddb004.sql021 where it's still ongoing (the last instance has a lot of tables)…
Date: 2021-04-21 19:02:07 UTC
clouddb004.sql021: 96%
clouddb005.sql021: 100%
clouddb006.sql021: 100%
clouddb007.sql021: 61%
clouddb008.sql021: 52%
clouddb009.sql021: 100%
Date: 2021-04-21 18:13:18 UTC
clouddb002.sql021: 100%
clouddb003.sql021: 100%
clouddb004.sql021: 96%
clouddb005.sql021: 59%
clouddb006.sql021: 89%
clouddb007.sql021: 48%
clouddb008.sql021: 42%
clouddb009.sql021: 68%
Date: 2021-04-21 16:19:55 UTC
The intervention is still in progress on clouddb00{2,3}.sql021.
Starting on clouddb00[4-9].sql021, on MySQL 5.5 instance only for now…
Date: 2021-04-21 15:08:26 UTC
The intervention is still in progress…
Date: 2021-04-21 12:16:21 UTC
The intervention is starting on clouddb00{2,3}.sql021, on MySQL 5.5 instance only for now…
Date: 2021-04-20 19:50:40 UTC
Intervention completed successfully on clouddb001.sql021, MySQL 5.5 instance only. 26042 tables converted on 311 databases.
Next intervention tomorrow.
Date: 2021-04-20 19:15:30 UTC
The intervention is still ongoing on clouddb001.sql021. 243 databases dumped, 20187 tables converted for now…
Date: 2021-04-20 18:51:26 UTC
The intervention is still ongoing on clouddb001.sql021. 174 databases dumped, 13200 tables converted for now…
Date: 2021-04-20 17:19:01 UTC
The noted average conversion time per table is about 0.10 second.
Date: 2021-04-20 17:00:36 UTC
The intervention is starting on clouddb001.sql021, on MySQL 5.5 instance only for now…
Les instances concernées sont relativement peu nombreuses. Il s'agit d'instances:
- Créées avant 2017
- et portant un nom préfixé par «sqlprive-»
- et hébergées sur le cluster sql021
- et contenant des tables InnoDB ayant été créées sur une version de MySQL strictement inférieure à 5.5 (MyISAM étant à l'époque le format par défaut)
- et utilisant le format de fichier InnoDB \"Antelope\"
Ces erreurs sont dues à un vieux format de fichier Antelope qui n'est plus supporté en version 8.0. Attention, sur MySQL 8.0, le format Antelope est toujours supporté, même si c'est la première version de MySQL où il n'est plus possible de créer des tables avec ce format. Ce qui n'est plus supporté, ce sont les tables Antelopes créées dans une version strictement inférieure à MySQL 5.5.
Afin de corriger durablement ce problème et vous permettre de migrer vers MySQL 8.0, nous allons migrer toutes les tables des CloudDB MySQL ayant un format de fichier Antelope pour les passer en Barracuda. Les autres tables (MyISAM ou InnoDB Barracuda) resteront inchangées. Un dump des bases concernées sera fait juste avant la migration. Vous retrouverez ces dumps dans votre Control Panel, à côté des autres dumps quotidiens.
Ces migrations seront faites mardi 2021-04-20, mercredi 2021-04-21, lundi 2021-04-26 et mardi 2021-04-27. Aucune coupure n'est à prévoir, juste un lock des tables allant de quelques dixièmes de secondes pour les tables les plus petites, à quelques minutes pour les plus grosses.
---
On very old MySQL CloudDB WebHosting instances, we noticed failing upgrades when moving from MySQL 5.7 to 8.0.
Impacted instances are relatively few. These are instances:
- Created before 2017
- and prefixed with \"sqlprive-\"
- and hosted on the sql021 cluster
- and having InnoDB tables created on a MySQL version strictly less than 5.5 (MyISAM was the default format then)
- and using the InnoDB file format \"Antelope\"
Those errors are due to an old Antelope file format that is no more supported in the 8.0 version. Warning, on MySQL 8.0, the Antelope format is still supported, even if this is the first version where you can not create tables using that
format. What is no more supported are the Antelope tables created in a version striclty less than MySQL 5.5.
To sustainably fix this issue and allow you to migrate to MySQL 8.0, we will migrate all the CloudDB MySQL tables having an Antelope file format to move them to Barracuda. The other tables (MyISAM or InnoDB Barracuda) will be kept unchanged. A dump of the concerned databases will be done just before the migration. You'll find those dumps in your Control Panel, next to the other daily dumps.
Those migrations will be done on Tuesday 2021-04-20, Wednesday 2021-04-21, Monday 2021-04-26 and Tuesday 2021-04-27. No downtime, only table locks during few millisecs for the smallest tables to a few minutes for the biggest ones.
Update(s):
Date: 2021-04-29 15:17:14 UTC
Intervention completed successfully on all the MySQL 5.5 of the sql021 cluster.
Another Travaux Task will be opened for the MySQL 5.6 and 5.7 parts.
Date: 2021-04-29 14:48:29 UTC
clouddb031.sql021: 100%
clouddb032.sql021: 100%
clouddb036.sql021: 98%
clouddb038.sql021: 100%
clouddb039.sql021: 100%
clouddb041.sql021: 94%
clouddb043.sql021: 71%
Date: 2021-04-29 13:25:37 UTC
The intervention is continuing on the host that had not been completed yesterday…
Date: 2021-04-28 20:17:49 UTC
clouddb030.sql021: 100%
clouddb031.sql021: 83%
clouddb032.sql021: 67%
clouddb033.sql021: 100%
clouddb035.sql021: 100%
clouddb036.sql021: 40%
clouddb038.sql021: 86%
clouddb039.sql021: 93%
clouddb041.sql021: 42%
clouddb042.sql021: 100%
clouddb043.sql021: 13%
Intervention will continue tomorrow.
Date: 2021-04-28 16:30:30 UTC
intervention is continuing on the host that had not been completed yesterday + on clouddb04[1-3].sql021.
Date: 2021-04-27 21:19:01 UTC
clouddb029.sql021: 100%
clouddb030.sql021: 74%
clouddb031.sql021: 64%
clouddb032.sql021: 67%
clouddb033.sql021: 94%
clouddb034.sql021: 100%
clouddb035.sql021: 40%
clouddb036.sql021: 15%
clouddb037.sql021: 100%
clouddb038.sql021: 86%
clouddb039.sql021: 65%
clouddb040.sql021: 100%
Intervention will continue tomorrow.
Date: 2021-04-27 20:25:39 UTC
clouddb029.sql021 and clouddb03[0-6].sql021: still ongoing…
clouddb03[7-9].sql021 and clouddb040.sql021: starting…
Date: 2021-04-27 19:42:11 UTC
clouddb02[5-8].sql021: done
clouddb0{29,30,31,32}.sql021: still ongoing…
clouddb03[3-6].sql021: starting…
Date: 2021-04-27 18:37:17 UTC
clouddb02{0,2,3,4}.sql021: done
clouddb02[5-8].sql021: still ongoing…
clouddb0{29,30,31,32}.sql021: starting…
Date: 2021-04-27 15:57:40 UTC
The intervention is continuing on clouddb02{0,2,3,4}.sql021 and starting on clouddb02[5-8].sql021…
Date: 2021-04-26 22:33:45 UTC
clouddb018.sql021: 100%
clouddb019.sql021: 100%
clouddb020.sql021: 51%, will be completed tomorrow
clouddb021.sql021: 100%
clouddb022.sql021: 62%, will be completed tomorrow
clouddb023.sql021: 95%, will be completed tomorrow
clouddb024.sql021: 60%, will be completed tomorrow
Date: 2021-04-26 21:04:06 UTC
clouddb012.sql021: 100%
clouddb015.sql021: 100%
clouddb016.sql021: 100%
clouddb017.sql021: 100%
clouddb018.sql021: 63%
clouddb019.sql021: 80%
clouddb020.sql021: 14%
clouddb021.sql021: 41%
clouddb022.sql021: 11%
clouddb023.sql021: 12%
clouddb024.sql021: 17%
Date: 2021-04-26 20:35:28 UTC
clouddb012.sql021: 93%
clouddb015.sql021: 70%
clouddb016.sql021: 91%
clouddb017.sql021: 68%
clouddb018.sql021: 36%
clouddb019.sql021: 67%
clouddb02[0-4].sql021: starting…
Date: 2021-04-26 20:01:43 UTC
clouddb012.sql021: 54%
clouddb015.sql021: 30%
clouddb016.sql021: 64%
clouddb017.sql021: 36%
clouddb018.sql021: 06%
clouddb019.sql021: 25%
Date: 2021-04-26 19:01:31 UTC
clouddb011.sql021: 100%
clouddb012.sql021: 35%
clouddb013.sql021: 100%
clouddb014.sql021: 100%
clouddb015.sql021: 27%
clouddb016.sql021: 60%
clouddb01[7-9].sql021: starting…
Date: 2021-04-26 17:14:04 UTC
clouddb010.sql021: 100%
clouddb011.sql021: 60%
clouddb012.sql021: 26%
clouddb013.sql021: 72%
clouddb014.sql021: 71%
clouddb01{5,6}.sql021: starting…
Date: 2021-04-26 16:32:56 UTC
clouddb010.sql021: 54%
clouddb011.sql021: 17%
clouddb012.sql021: 17%
clouddb013.sql021: 19%
clouddb014.sql021: 22%
Date: 2021-04-26 15:56:42 UTC
The intervention is starting on clouddb01{0-4}.sql021, on MySQL 5.5 instance only for now…
Date: 2021-04-21 20:34:45 UTC
Intervention completed successfully. All the MySQL 5.5 instances are OK on clouddb00[1-9].sql021.
Next intervention on Monday 2021-04-26.
Date: 2021-04-21 20:10:01 UTC
Intervention completed, except on clouddb004.sql021 where it's still ongoing (the last instance has a lot of tables)…
Date: 2021-04-21 19:02:07 UTC
clouddb004.sql021: 96%
clouddb005.sql021: 100%
clouddb006.sql021: 100%
clouddb007.sql021: 61%
clouddb008.sql021: 52%
clouddb009.sql021: 100%
Date: 2021-04-21 18:13:18 UTC
clouddb002.sql021: 100%
clouddb003.sql021: 100%
clouddb004.sql021: 96%
clouddb005.sql021: 59%
clouddb006.sql021: 89%
clouddb007.sql021: 48%
clouddb008.sql021: 42%
clouddb009.sql021: 68%
Date: 2021-04-21 16:19:55 UTC
The intervention is still in progress on clouddb00{2,3}.sql021.
Starting on clouddb00[4-9].sql021, on MySQL 5.5 instance only for now…
Date: 2021-04-21 15:08:26 UTC
The intervention is still in progress…
Date: 2021-04-21 12:16:21 UTC
The intervention is starting on clouddb00{2,3}.sql021, on MySQL 5.5 instance only for now…
Date: 2021-04-20 19:50:40 UTC
Intervention completed successfully on clouddb001.sql021, MySQL 5.5 instance only. 26042 tables converted on 311 databases.
Next intervention tomorrow.
Date: 2021-04-20 19:15:30 UTC
The intervention is still ongoing on clouddb001.sql021. 243 databases dumped, 20187 tables converted for now…
Date: 2021-04-20 18:51:26 UTC
The intervention is still ongoing on clouddb001.sql021. 174 databases dumped, 13200 tables converted for now…
Date: 2021-04-20 17:19:01 UTC
The noted average conversion time per table is about 0.10 second.
Date: 2021-04-20 17:00:36 UTC
The intervention is starting on clouddb001.sql021, on MySQL 5.5 instance only for now…
This scheduled maintenance affected: Web Hosting || Datacenter GRA (Cluster002, Cluster003, Cluster006, Cluster007, Cluster011, Cluster012, Cluster013, Cluster014, Cluster015, Cluster017, Cluster020, Cluster021, Cluster023, Cluster024, Cluster025, Cluster026, Cluster027, Cluster028, Cluster029, Cluster030, Cluster031).