Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
-
While deploying a client extension to an Liferay SaaS EXT environment the following error is thrown:
Some error has happened during the build. Try again. [{"message":"Exceeded Quota Limit","status":403,"errors":[{"reason":"exceededPlanMaximum","context":{"message":"Desired service spec cpu exceeded the max limit for provided plan ext<projectID-projectName>. The max limit is 1","param":"cpu","attemptUsage":2,"quotaMax":1}}]}].
Environment
- Liferay SaaS, specifically Liferay SaaS - Pro accounts
Resolution
- The Liferay SaaS - Pro account offers 1 vCPU and 1 GB of memory.
- If you encounter this error, please adjust the "cpu" field in the LCP.json files to ensure that the sum total of all of the deployments to the EXT environment are less than or equal to "1".
-
Example 1: If we are deploying two client extensions to the EXT environment, we can define in the LCP.json file
"cpu": 0.5on both services to come to a total of "1". - Example 2: We can set up 8 client extensions with the "cpu" value of 0.1, which would equate to 0.8 in total. We can then add a 9th client extension with the "cpu" value of 0.2, and this would equate to 1 vCPU in total.
-
Example 1: If we are deploying two client extensions to the EXT environment, we can define in the LCP.json file
Additional Information
- Reference to LCP.json configuration:
How does the "environments" configuration on LCP.json work? - Description of specifications and limitations of different Liferay SaaS plans:
Liferay SaaS Plans
Should you require additional resources, please contact your Liferay Account Executive to determine if the purchase of Additional Extension Capacity add-ons are suitable for the success of your project.