Multiple AppEngine 104 errors
57 views
Skip to first unread message
Alexandru Farcaş
Apr 28, 2016, 6:06:08 AM4/28/16
to Google App Engine
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.
Ice13ill
Apr 28, 2016, 6:17:43 AM4/28/16
to Google App Engine
Same for me.
Also, many 500 and 404 errors and very high latencies.Alexandru Farcaş
Apr 28, 2016, 6:43:15 AM4/28/16
to Google App Engine
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 ..
Ice13ill
Apr 28, 2016, 1:13:34 PM4/28/16
to Google App Engine
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.
Nick (Cloud Platform Support)
Apr 28, 2016, 4:51:58 PM4/28/16
to Google App Engine
Hey Alexandru & Ice13ill,
These error codes represent several different issues.
500 means an internal server error, which is not specific enough to determine a cause unless you check the logs of your app / server.
404 means a resource was requested but not found, most often since no request handler is configured for the route requested.
104 is an App Engine error code used when concurrent requests are not configured on your app (threadsafe is false in app.yaml or appengine-web.xml)
Finally, ConcurrentModificationExceptioYou can read about how to avoid this in the documentationn is an error relating to the concurrent modification of a Datastore entity group too often in a given timeframe. You can read about how to avoid this in the documentation [1], [2].
If you could post the full stack traces / error logs, this would greatly increase anybody's ability to determine what was happening.
Now that the issues have resolved, it's possible that it may simply be beyond anyone to try to determine what's happening. Feel free to ask any questions you may have, I'll be happy to help.
Sincerely,
Nick
Cloud Platform Community Support
These error codes represent several different issues.
500 means an internal server error, which is not specific enough to determine a cause unless you check the logs of your app / server.
404 means a resource was requested but not found, most often since no request handler is configured for the route requested.
104 is an App Engine error code used when concurrent requests are not configured on your app (threadsafe is false in app.yaml or appengine-web.xml)
Finally, ConcurrentModificationExceptioYou can read about how to avoid this in the documentationn is an error relating to the concurrent modification of a Datastore entity group too often in a given timeframe. You can read about how to avoid this in the documentation [1], [2].
If you could post the full stack traces / error logs, this would greatly increase anybody's ability to determine what was happening.
Now that the issues have resolved, it's possible that it may simply be beyond anyone to try to determine what's happening. Feel free to ask any questions you may have, I'll be happy to help.
Sincerely,
Nick
Cloud Platform Community Support
Reply all
Reply to author
Forward
0 new messages