Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

The database service went offline briefly causing downtime

Written By

Brian Suh

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • The database service went offline briefly causing downtime

Environment

  • Liferay PaaS

Resolution

  • The database service performs routine maintenance which runs for a few minutes. This will take the database service down briefly and bring it back up again once the maintenance has completed.
  • This maintenance window takes place during a specifiable date and time through the LCP.json file. If you do not specify the date and time, the default values will be set, and will be executed accordingly.
  • To ensure that the database maintenance window is set during an optimal and predictable time for your Liferay PaaS environment, please review the Database Maintenance Window Variables section of our Database Service (MySQL) documentation. You can specify the date, time (in UTC) and the channel in the LCP.json file.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?