rssLink RSS for all categories
 
icon_red
icon_green
icon_green
icon_red
icon_red
icon_green
icon_green
icon_red
icon_red
icon_red
icon_blue
icon_green
icon_green
icon_orange
icon_green
icon_blue
icon_green
icon_red
icon_red
icon_red
icon_green
icon_orange
icon_green
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_green
icon_red
 

FS#44194 — CloudDB (PrivateSQL)

Attached to Project— Web Hosting / CloudDB
Amélioration
GRA / All clusters
CLOSED
100%
Depuis maintenant 2 mois, nous travaillons à faire en sorte que vos instances CloudDB (également connues sous le nom «PrivateSQL») gèrent leur mémoire plus intelligemment. Nos tests sont concluants, il est maintenant temps de passer à la production!

Cette amélioration entraînera le redémarrage de votre instance et entraînera donc une coupure de 2 minutes environ.

Vous trouverez le planning détaillé dans les commentaires.

Des questions? Des retours à nous faire? C’est ici: https://community.ovh.com/t/amelioration-de-la-gestion-de-la-memoire-sur-les-clouddb/28070

---

For the past 2 months, we have been working so that your CloudDB instances (also known as “PrivateSQL”) handle their memory in a smarter way. Our tests are conclusive, now it is time to move on production!

This improvement requires restarting your instance and therefore about 2 minutes downtime.

You’ll find the detailed planning in the following comments.

Any questions? Any feedbacks? You can do it here: https://community.ovh.com/t/amelioration-de-la-gestion-de-la-memoire-sur-les-clouddb/28070 ; This thread is in French, but do not hesitate to write in English, we’ll answer you.
Date:  Thursday, 09 July 2020, 00:29AM
Reason for closing:  Done
Comment by OVH - Wednesday, 22 April 2020, 21:26PM

Next interventions:
- 2020-04-23, from 23:00 CET: clouddb005.sql008, part 1/3 (you won’t see any changes there, except the 1 minute downtime)
- 2020-04-27, from 23:00 CET: clouddb005.sql008, part 2/3 (half of the instances will see the changes)
- 2020-04-28, from 23:00 CET: clouddb005.sql008, part 3/3


Comment by OVH - Thursday, 23 April 2020, 23:10PM

Intervention completed. Downtime: from 23:07 to 23:08 CET.


Comment by OVH - Tuesday, 28 April 2020, 23:53PM

The intervention is starting on clouddb005.sql008…


Comment by OVH - Wednesday, 29 April 2020, 00:02AM

Intervention completed successfully.


Comment by OVH - Monday, 04 May 2020, 20:23PM

Next interventions:
- 2020-05-04, from 23:00 CEST: clouddb010.sql008
- 2020-05-05, from 23:00 CEST: clouddb01[1-2].sql008
- 2020-05-06, from 23:00 CEST: clouddb0[01,13-19].sql008


Comment by OVH - Monday, 04 May 2020, 23:51PM

Intervention completed.
Downtime on cloudddb010.sql008: from 23:40 to 23:50 CEST (about 2 minutes per instance, in this time slot).


Comment by OVH - Wednesday, 06 May 2020, 00:07AM

Intervention completed.
Downtime on cloudddb01[1-2].sql008: from 23:52 to 00:07 CEST (about 2 minutes per instance, in this time slot).


Comment by OVH - Thursday, 07 May 2020, 00:25AM

Intervention completed on cloudddb0[13-19].sql008: downtime from 23:30 to 00:15 CEST (about 2 minutes per instance, in this time slot).
clouddb001.sql008 does not restart as expected. Investigation in progress.


Comment by OVH - Thursday, 07 May 2020, 01:29AM

clouddb001.sql008 restarted. It took a long time. Due to a bug in Docker, its status was inconsistent. It is now fixed. Continuing the intervention on this host…


Comment by OVH - Thursday, 07 May 2020, 01:47AM

Intervention completed.


Comment by OVH - Wednesday, 13 May 2020, 17:07PM

As detailed on https://community.ovh.com/t/amelioration-de-la-gestion-de-la-memoire-sur-les-clouddb/28070, we have a new improvement.
This one will be deployed on clouddb001.sql008 on 2020-05-13.


Comment by OVH - Wednesday, 13 May 2020, 20:35PM

Deployment done on clouddb001.sql008.
Downtime: from 20:30 to 20:32 CEST.
Next part (clouddb0[05,10-19].sql008) tomorrow.


Comment by OVH - Thursday, 14 May 2020, 15:33PM

Deployment done on clouddb013.sql008.
Downtime: from 15:30 to 15:32 CEST.


Comment by OVH - Thursday, 14 May 2020, 23:02PM

Deployment done on clouddb005.sql008.
Downtime: from 22:53 to 23:02 CEST.


Comment by OVH - Thursday, 14 May 2020, 23:27PM

Deployment done on clouddb0[01-12,14-19].sql008.
Downtime: from 23:19 to 23:27 CEST.


Comment by OVH - Tuesday, 02 June 2020, 21:52PM

Before going further in the massive deployment of the solution, we will first deploy a requirement everywhere: changing the Docker cgroups hierarchy. To do so, we need to restart your instance. A 2 minutes downtime is expected.

Next interventions:
- sql008 (except clouddb0[01,05,10-19].sql008, already up-to-date) on Thursday, 2020-06-04
- sql006 on Monday, 2020-06-08
- sql007 on Tuesday, 2020-06-09
- sql020 on Wednesday, 2020-06-10
- sql021 on Thursday, 2020-06-11

All the interventions start from 23:00 CEST.


Comment by OVH - Thursday, 04 June 2020, 22:59PM

The intervention is starting on sql008…


Comment by OVH - Thursday, 04 June 2020, 23:34PM

clouddb0[01-23].sql008 are up-to-date. Continuing the intervention…


Comment by OVH - Thursday, 04 June 2020, 23:50PM

Intervention completed successfully on sql008.


Comment by OVH - Monday, 08 June 2020, 23:03PM

The intervention is starting on sql006…


Comment by OVH - Monday, 08 June 2020, 23:20PM

clouddb0[01-19].sql006 are up-to-date. Continuing the intervention…


Comment by OVH - Monday, 08 June 2020, 23:58PM

All the VM are up-to-date but clouddb072.sql006 (the intervention is continuing on this last one)…


Comment by OVH - Tuesday, 09 June 2020, 00:31AM

clouddb072.sql006 is UP and running. Sorry for the delay for this host.
Intervention completed.


Comment by OVH - Tuesday, 09 June 2020, 23:00PM

The intervention is starting on sql007…


Comment by OVH - Tuesday, 09 June 2020, 23:26PM

clouddb0[01-29].sql007 are up-to-date. Continuing the intervention…


Comment by OVH - Tuesday, 09 June 2020, 23:32PM

Intervention completed successfully.


Comment by OVH - Wednesday, 10 June 2020, 23:11PM

The intervention is starting on sql020…


Comment by OVH - Wednesday, 10 June 2020, 23:37PM

Intervention completed successfully.


Comment by OVH - Thursday, 11 June 2020, 23:24PM

The intervention is starting on sql021…


Comment by OVH - Thursday, 11 June 2020, 23:55PM

Intervention completed successfully.


Comment by OVH - Thursday, 02 July 2020, 21:58PM

Time to finish that =)

Next intervention:
- Monday 2020-07-06: sql008 (clouddb0[01,05,10-19].sql008 is already up-to-date)


Comment by OVH - Monday, 06 July 2020, 23:02PM

The intervention is starting…


Comment by OVH - Monday, 06 July 2020, 23:41PM

clouddb0[01-24].sql008 are up-to-date. Continuing…


Comment by OVH - Tuesday, 07 July 2020, 00:08AM

Intervention completed successfully.
Next intervention tomorrow (2020-07-07), from 23:00 CEST:
- sql006
- sql007


Comment by OVH - Tuesday, 07 July 2020, 19:15PM

And the following intervention will be on 2020-07-08, from 23:00 CEST:
- sql020
- sql021
- sql059


Comment by OVH - Tuesday, 07 July 2020, 23:28PM

The intervention is starting on sql006 and sql007…


Comment by OVH - Tuesday, 07 July 2020, 23:46PM

clouddb00[1-9].sql006: done.
clouddb00[1-4].sql007: done.
Continuing…


Comment by OVH - Wednesday, 08 July 2020, 00:15AM

clouddb0[01-39].sql006: done.
clouddb0[01-24].sql007: done.
Continuing…


Comment by OVH - Wednesday, 08 July 2020, 00:46AM

Intervention completed successfully on sql006 and sql007.

As a reminder, the next intervention will be done tomorrow (2020-07-08), from 23:00 CEST:
- sql020
- sql021
- sql059


Comment by OVH - Wednesday, 08 July 2020, 23:13PM

The intervention is starting on sql020 and sql021…


Comment by OVH - Wednesday, 08 July 2020, 23:25PM

sql020: clouddb00[1-4]: done. Continuing…
sql021: clouddb00[1-4]: done. Continuing…
sql059: Starting…


Comment by OVH - Wednesday, 08 July 2020, 23:33PM

sql020: clouddb00[1-9]: done. Continuing…
sql021: clouddb00[1-9]: done. Continuing…
sql059: done. (that's a tiny cluster for now)


Comment by OVH - Thursday, 09 July 2020, 00:28AM

Intervention completed successfully.

I personally think that this is a great step forward. Enjoy =)