25 May 2020: The majority of Production clusters have now been migrated and the migration operation will be closing out in the near future. Instaclustr is still keeping a close eye on all clusters to see if there is any noticeable effects as a result of the migration, however we have not yet seen any. A small group of customers/clusters remain to be migrated, but scheduling for all of these has now been carried out and they will be completed over the coming two weeks.
30 April 2020: The Debian migration is currently well underway with the vast majority of our customers development and non-production environments that utilise AWS migrated successfully. Further scheduled work will continue in the coming weeks to finalise all of the development/non-production AWS clusters. Instaclustr will also start proceeding with production AWS migrations in the coming weeks.
Posted Apr 24, 2020 - 02:40 UTC
Scheduled
Instaclustr are performing operating system replacements across all clusters over the coming months. While this is a relatively significant change, the impact to our customers is expected to be very similar to our regular operating system patching program. That is, the change will require a rolling restart of each cluster, however this will be completed without loss of quorum for all Cassandra and Kafka clusters and so we advise that customers should not see an interruption to service.
For all PRODUCTION clusters, and clusters running Spark, customers will receive a further notification prior to patching to confirm a specific maintenance window.
Schedules for the maintenance have been sent out individually to all customers, and we advise that customers refer to the scheduling included in this notification for more accurate information on their specific maintenance timeframe.
Further background information:
Instaclustr is in the process of scheduling all of our nodes to undergo a base operating system migration from CoreOS to our latest platform offering, which utilises Debian. We have been planning this migration activity for quite some time and we are now pushing forward with the replacement. This activity has been necessitated by the forthcoming end of life for CoreOS (End-of May 2020) but will bring us advantages such as earlier access to new cloud provider offerings and greater availability of relevant public security benchmarks. We have conducted thorough functionality and performance testing prior to moving to the deployment phase of this change and do not expect any adverse impacts. We are also following an incremental roll-out approach across our managed fleet (as outlined above) and will be closely monitoring for any issues through that roll-out.