The read-only error experienced with your DB is related to an issue with the legacy HA mode for Cloud SQL. Cloud SQL checks the availability of the master instance using different checkpoints to know if the instance is healthy and in particular, one of them is the writability of the disk; in case the master is not ok because of the writability, the traffic will be routed to the failover replica causing the state of the DB to be "read-only.
The long-term solution is to set up an HA mode that does not use an explicit failover replica.
The new HA replication mode has some added benefits such as increased replication performance and will have no cost implications for our customers
The Liferay team will coordinate with customers to provide a detailed path to perform this migration. Meanwhile, should the behavior happen the recommended workaround is to restart the Liferay service.
Posted Apr 29, 2021 - 17:23 PDT
Identified
Some customers are experiencing an error that limits their database service to read-only operations. The root cause of this error is related to a change in the underlying HA configuration by our infrastructure partner.
This error can be fixed by restarting the Liferay Service.
We are working to prevent this from happening again and new information will be posted soon.
If you have questions or need further assistance, please open a Support ticket.