+1 Anu
This is the second time in the past 4 months we faced a P1 issue which took 
2 days to get resolved.

@Google team, 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.

On Saturday, March 24, 2018 at 10:32:14 PM UTC+5:30, Suvodeep Pyne wrote:
>
> We are also facing the same issue. The LB is throwing 502's 
> intermittently. 
>
> A simple parallel curl with 30 requests is able to choke up the LB 5 - 8 
> times. Our App servers are healthy and are not receiving the requests.
>
>
> On Saturday, March 24, 2018 at 2:14:21 AM UTC+5:30, Navi Aujla (Google 
> Cloud Support) wrote:
>>
>> Hello Anu
>>
>> As mentioned in my last message there are multiple factors which may 
>> cause this error. However, If you believe this to an issue with the GCP 
>> load balancer, I would suggest you to open a private issue report using this 
>> link 
>> <https://issuetracker.google.com/issues/new?component=187164&template=803901>[1]
>>  
>> providing the relevant detailed information for the investigation. 
>>
>>
>> On Friday, March 23, 2018 at 3:24:30 PM UTC-4, Anu V wrote:
>>>
>>> Backends are healthy, I found this 502 errors across my few projects 
>>> using AppEngine.
>>>
>>> All instances are able to access and work normally, I've tested using 
>>> curl to send a request directly to instance's private ip and it works all 
>>> the time.
>>>
>>>
>>> On Saturday, March 24, 2018 at 2:07:30 AM UTC+7, Navi Aujla (Google 
>>> Cloud Support) wrote:
>>>>
>>>> Hello Anu,
>>>>
>>>> The "*failed_to_connect_to_backend" *error message indicates that load 
>>>> balancer is failing to connect to backends. There could be many possible 
>>>> reasons for it. For example: Unhealthy instance if reported by health 
>>>> check, incorrect URL mapping 
>>>> <https://cloud.google.com/compute/docs/load-balancing/http/url-map>, 
>>>> high backend utilization causing backend not to respond to the load 
>>>> balancer requests. You can refer to this thread 
>>>> <https://groups.google.com/forum/#!topic/gce-discussion/mXmnB-Ab5Z4>for 
>>>> more information and check instance system/error and access logs. 
>>>>
>>>> On Friday, March 23, 2018 at 9:06:00 AM UTC-4, Anu V wrote:
>>>>>
>>>>> I'am experiencing too many 502 errors from Load Balance and the 
>>>>> instances are working fine. (
>>>>>
>>>>>
>>>>> @type: "
>>>>> type.googleapis.com/google.cloud.loadbalancing.type.LoadBalancerLogEntry" 
>>>>>
>>>>> statusDetails: "failed_to_connect_to_backend" 
>>>>>
>>>>> I've also found that this happen on my few projects starting about 12 
>>>>> hours ago, I've checked https://status.cloud.google.com/ and it said 
>>>>> all working fine.
>>>>> I cannot upgrade support level to create the ticket, so I am posting 
>>>>> it here to ask if anyone having the same problem as I am?
>>>>>
>>>>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/8b30e604-9db0-478f-8e5e-cce4448f3e33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to