I've already paid for a support and result is the same. No fix in timely manner, no reply, no nothing.
Here's their quote regards this issue: As of the moment, they confirmed that the 502 errors seem to be coming from the Cloud L2 Google Front End (GFE) and with error message "failed_to_connect_to_backend". They are still investigating about the connection. However, they confirmed that deployments are still fine and they are looking further if there is a certain subset where the backend is unable to be connected to from a GFE. (My Support Case is: Case/0016000001LHlyt/U-15342525) At least gcloud support team should share this information among them, not to mention that they should raise this issue on service status page. And yeah, we're on the same boat, referring thread: https://groups.google.com/forum/#!topic/google-appengine/nmbstD7wIls The thing that make me so angry is they keep telling that there's our fault without checking their service first. On Sunday, March 25, 2018 at 11:37:54 AM UTC+7, Suvodeep Pyne wrote: > > Hey Ani > > I agree that keeping a low service cost is important. But either you run a > perfect service or you engage with the customer. I have seen 3 P1s causing > service disruption (which Google fixed) in the last 4 months and some other > issues causing a degraded service. Clearly, the first one isn't the case. > As a customer paying for the service, I don't expect to be redirected to > stackoverflow to report platform errors. So I believe there is a problem > that needs to be addressed. > > And yes, I posted on issuetracker > <https://issuetracker.google.com/issues/76200991> as well. It is nearing > 24 hours now and the bug hasn't even been assigned yet. > > Anyways, thank you and all the best to you too. > > On Sunday, March 25, 2018 at 9:12:51 AM UTC+5:30, Ani Hatzis wrote: >> >> Hey Suvodeep, I understand the frustration, but from my point of view, I >> prefer to pay just for the resources I use and according to the SLA. I >> wouldn't want to indirectly pay for free premium support of other customers >> (which probably would increase all prices significantly). Anyway, wish you >> the best. >> >> On 25 March 2018 at 05:11, Suvodeep Pyne <[email protected]> wrote: >> >>> Hey Jordan >>> >>> Thanks for that info. Now, take a look at this. >>> >>> >>> <https://lh3.googleusercontent.com/-6zRqeMHQX2U/WrcQXBBS2xI/AAAAAAACjhk/-ahOt29lmuwhVlJGx6khLJy6AdytljcAwCLcBGAs/s1600/Screen%2BShot%2B2018-03-25%2Bat%2B8.26.49%2BAM.png> >>> >>> This is the second time in the past 4 months we faced a P1 issue which >>> took 2 days to get resolved. The LB was throwing 502s intermittently while >>> the app server was totally healthy. You can check my account for logs. And >>> btw, there were others who were complaining about the same issue >>> <https://groups.google.com/forum/#!topic/google-appengine/nmbstD7wIls>. >>> >>> Since as you mentioned that this is a forum for general product >>> discussions; I want you to note that this is perhaps not the best customer >>> experience. I am aware of your support tiers but there should be a better >>> interaction model with your customer. We are paying for the service and you >>> are answerable to us in case of outages/service disruption. >>> >>> Regards >>> >>> >>> On Sunday, March 25, 2018 at 4:17:23 AM UTC+5:30, Jordan (Cloud Platform >>> Support) wrote: >>>> >>>> This occurs when your actual application becomes too busy to respond to >>>> the nginx server Docker container that sits in front of your application >>>> Docker container within the instance. Nginx will send health checks >>>> <https://cloud.google.com/appengine/docs/flexible/java/configuring-your-app-with-app-yaml#health_checks> >>>> >>>> to your application in order to make sure it is responsive so that it may >>>> accept new requests. If your code blocks the main thread for too long, >>>> nginx will not receive any response from your app and will assume it is >>>> not >>>> healthy. This will produce a 502 Bad Gateway error when App Engine asks >>>> nginx if the application is ready to accept new requests, and the instance >>>> will be restarted in order to make it healthy again. >>>> >>>> It is therefore recommended to increase the number of instances you >>>> have (as I assume you are limiting your max to a very low number like >>>> one), >>>> and to ensure your code is properly configured to handle concurrent >>>> requests, returns quickly, and does not block the main thread for too >>>> long. >>>> You can also configure the health checks >>>> <https://cloud.google.com/appengine/docs/flexible/java/configuring-your-app-with-app-yaml#updated_health_checks> >>>> >>>> as to not render your instance as unhealthy so quickly and to give it more >>>> time to recover from traffic spikes. >>>> >>>> - Note that Google Groups is reserved for general product discussions >>>> and not for technical support. For further technical support it is >>>> recommended to post your detailed questions >>>> <https://stackoverflow.com/help/how-to-ask>to Stack Overflow >>>> <https://cloud.google.com/support/docs/stackexchange> using the >>>> supported Cloud tags. >>>> >>> -- >>> 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/e6ba838b-5def-4a14-8243-dda691f4fa64%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/google-appengine/e6ba838b-5def-4a14-8243-dda691f4fa64%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- 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/d79cdef8-b2c3-4084-aec7-cea0f931d366%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
