After a while, it seams everything went back to normal, but I think there were 60-70 minutes with severe impact on request handling. Because of 104, 404, 500 errors, many tasks could not be executed and a very high retry rate caused high latencies and lots of spawned instances.
It's very strange that nobody else seamed to had this issue and also, nobody from google sent an email or reply to this thread. On Thursday, April 28, 2016 at 1:43:15 PM UTC+3, Alexandru Farcaş wrote: > > In the last 20 minutes I didn't received 104 errors and the tasks were > created with success! > It seems that the application is running as it used to run .. > > On Thursday, April 28, 2016 at 1:17:43 PM UTC+3, Ice13ill wrote: >> >> Same for me. >> Also, many 500 and 404 errors and very high latencies. >> >> On Thursday, April 28, 2016 at 1:06:08 PM UTC+3, Alexandru Farcaş wrote: >>> >>> Hi, >>> >>> I have multiple errors with error code 104. I have this behaviour since >>> 11:50am EEST. >>> I receive a lot of errors at task creation. I receive this errors but >>> the tasks are still created in task queue! >>> >>> java.util.ConcurrentModificationException >> too much contention on >>>> these datastore entities. please try again. >>> >>> >>> >>> >> -- 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/fe9dd608-2344-482b-896a-2d769e795854%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
