Hello Udit, you are most certainly getting those 502 errors because you've set a strict maximum number of instances even though it appears your application needs to handle heavy spikes in utilization. To mitigate these errors you could remove the maximum cap or rate-limit to stretch the spikes over a longer period of time.
As for the 502 response code, what's stopping you from handling it? How is your application used? On Monday, September 11, 2017 at 3:14:37 AM UTC-4, udit sharma wrote: > > > Hey all, > > I am using GAE for hosting my applications. I am facing a problem > related to load balancing error of 502 bad gateway. > > When the requests on the server surpass the load and GAE are yet to spin > up the instances to balance it, 502 bad gateway get thrown, which defines > the requests are failing. I wanted to know the ways of handling this error > from the backend/frontend, so that if the loads get more it will show to > the user "Servers are down" instead of the application gets crashed. > > I am handling the 500 backend error since whenever it happens response is > a JSON type: "message":"internal server error". > > Can I get something same for 502 error too like "message":"load balance > error"? > > I am a novice here, any help would be grateful. > > Thanks > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/ef42d22a-25c0-4bf8-b0ef-bc05b61dd0da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
