Issues related to shortage of compute resources

[dayeon]

Hello, I'm an undergraduate student from South Korea, interested in IaaS cloud services.
I'm currently investigating about the issues that occur due to lack of compute resources.

I'd like to ask if there's any compensation policy to an error message like below:
"The zone 'projects/PROJECT_ID/zones/ZONE' does not have enough resources available to fulfill the request.
Try a different zone, or try again later."

If such error occurs, do I get to receive any kind of compensation (ex. Financial Credits) for the issue?

Thank you ahead for your help.

[dionv]

Hello dayeon,

As per Mahmoud Shariff in StackOveflow post:

You’ve just encountered a stockout issue. A Stockout means that the particular GCP datacenter in that zone has reached its resource limit.

The Google Cloud Platform team are there to make sure that there are available resources in all zones. This type of issue is rare. When a situation like this occurs or is about to occur, the team is notified immediately, the issue is investigated and quickly fixed.

I recommend deploying and balancing your workload across multiple zones or regions to reduce the likelihood of a stockout. Please review the documentation which outlines how to build resilient and scalable architectures on the Google Cloud Platform.

As per your question about compensation, there is no rolling announcement on compensation for the said error. We do really apologize for the inconvenience and would recommend checking other zone or region to deploy your instances.

[ortegafernando]

Hi, do you have any spected time/date to solve this? Thanks.

[manishkjs]

To supplement what dayeon has mentioned, here is one of the support blogs which helps you figure out the next steps in case you face that error.

In general, the supplier and customer enters contract through SLA terms in which supplier is responsible for maintaining minimum uptime for the services which have been deployed or are currently being consumed. For example, Compute Engine VMs has various levels of SLAs depending on how service is deployed.

The compensation part you are referring to, probably was this. You can learn more about SLAs and agreements here.

Hope this helps.

[dayeon]

Hello, thank you for your reply.

I'd like to ask two more things related to the issue that occurs due to shortage of resources.

If an error occurs because of not enough resources, dionv told me that there isn't any compensation for the issue.

1. Does it mean that 'an issue due to not enough resources' is not considered as a 'failure'?
2. Does it mean that 'an issue due to not enough resources' does not have anything to do with the terms of the SLA?

Thank you so much for your help.

[manishkjs · Accepted solution]

1. True. The SLA is measured against deployed instances and their uptime. 
2. True. The article I shared earlier, goes into depth on what SLA means for Compute engine VMs. Stockouts are handled at best-effort basis. On the other hand, if you have started consuming the service, its uptime (SLA) obligation is with service provider.

Hope this helps.

[dayeon]

Thank you for your help, hope you have a great day! 🙂

[ortegafernando]

Sorry, the link that you have shared us says: "

• Because this situation is temporary and can change frequently based on fluctuating demand, try your request again later.

Do you have any expect time to solve this?  Help me, thanks.