Overview

Liferay Cloud is migrating all customer databases to MySQL 8 as MySQL 5.7 has reached end-of-life (EoL) and will no longer receive critical updates. This migration ensures continued security, performance, and compatibility across all environments. The migration consists of two main steps:

1. Upgrading all customer database services to version 5.2.0.
2. Scheduling database server upgrades to MySQL 8, including predefined and flexible time slots for different environments.

This article outlines the migration plan, scheduling options, and required testing steps.

Database Service Version Bump to 5.2.0

To ensure compatibility with MySQL 8, all customer database services between versions 5.0.0 and below 5.2.0 will need to be upgraded to version 5.2.0.

• Starting November 12, 2024:
  • Upon the next service deployment , database services running versions between 5.0.0 and below 5.2.0 will be automatically upgraded to version 5.2.0.
  • Only the database service version will be modified; other parameters in the LCP.json configuration will remain unchanged.
  • Version 5.2.0 is compatible with all Liferay Cloud services below 5.2.0, ensuring no disruptions.
  • Database services running on 4.x versions will not be automatically upgraded at this stage.
• December 3, 2024:
  • If database services have not been upgraded to version 5.2.0 by this date, they will be automatically redeployed with this version. NO DOWNTIME will occur for this upgrade.

Database Server Upgrade to MySQL 8 with Downtime

Starting in December 2024, Liferay Cloud will begin scheduled upgrades of MySQL database servers to MySQL 8. These upgrades require downtime, ranging from 30 minutes to up to 3 hours, depending on database size and configuration.

• Predefined Upgrade Slots: Two separate slots are provided for each customer:
  • Lower Environments (e.g., DEV, UAT): Scheduled first to allow testing before production.
  • Production Environments (e.g., PRD, DR): Scheduled after lower environments to ensure smooth transitions.
• Maintenance Windows: Upgrades will occur on Tuesdays and Thursdays, 8 am to 8 pm PST.
• Scheduled Dates:
  • December 2024: December 10, December 12, December 17
  • January 2025: January 7, January 9, January 14, January 16, January 21, January 23, January 28, January 30

Required Customer Action for Testing in Lower Environments

After upgrading lower environments (e.g., DEV, UAT), customers must verify that applications function as expected. Testing in lower environments allows time to address potential compatibility adjustments on the application layer before the production upgrade. If issues arise, please open a support ticket.

Flexible Rescheduling Options

If your assigned upgrade slot does not meet your operational needs, you may request an alternative date and time, including weekends.

• Reschedule Deadline: Submit rescheduling requests via a support ticket by January 21, 2025.
• Support Ticket Submission: Use your Liferay Cloud console to request your preferred slot.

Key Dates for MySQL 8 Migration

Support and Contact Information

Prioritization of Support Requests

Our support team will prioritize tickets related to the database service upgrades, MySQL 8 migration scheduling, and rescheduling requests.

How to Reach Support

For any questions or issues, customers can open a support ticket through the Liferay Cloud console. Our team is ready to help ensure a smooth transition.

 

FAQs

Why is this MySQL 8 migration necessary?
With the end-of-life (EoL) for MySQL 5.7, it is essential to upgrade to MySQL 8 to maintain security, performance, and compatibility. MySQL 5.7 no longer receives updates, including critical security patches, which could expose customer databases to vulnerabilities and performance limitations over time.

Are MySQL 5.7 backups compatible with MySQL 8?
Yes, MySQL 5.7 backups should generally be compatible with MySQL 8, allowing for successful restores if needed. While our extensive testing has shown no issues with backup compatibility, there remains an extremely low probability that a restored database might cause unexpected behavior at the application level or, in rare cases, fail to restore entirely. We recommend monitoring applications closely after any restore and reaching out to support if unexpected behavior arises.

What if issues arise during the MySQL 8 migration?
If any issues occur during the migration, the process will automatically roll back, keeping your database on MySQL 5.7 to maintain stability. In such cases, our support team will work closely with you to diagnose and resolve the issue before scheduling a new upgrade attempt.

Why is it important to test in lower environments first?
Testing in lower environments, such as DEV and UAT, is critical to identify and address any compatibility issues that may arise before production upgrades. This approach minimizes the risk of disruptions in your production environment, ensuring that any necessary adjustments are completed early in the migration process.

How can I reschedule my MySQL 8 upgrade?
If the predefined upgrade slot is not convenient for your team, you may submit a support ticket through the Liferay Cloud console to request a new date and time. To ensure availability, please submit your request by January 21, 2025.

Why did Liferay wait to ask customers to upgrade to MySQL 8?
Liferay adopted a phased approach, prioritizing SaaS environments for MySQL 8 upgrades first. This initial focus allowed our teams to streamline and refine the upgrade process, addressing potential issues early on. By the time we reached PaaS customers, we were equipped to offer a smooth migration experience with minimized risks and disruption. Additionally, the three-month upgrade window we provide strikes a balance between urgency and flexibility, aligning with industry practices to ensure a secure, high-performance database environment.