--To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/UrfiFXjdiTcJ.
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
http://groups.google.com/group/google-appengine/browse_thread/thread/6575ff4a0683bb6b
On Dec 6, 5:32 pm, "Johan Euphrosine (Google)" <pro...@google.com>
wrote:
DeadlineExceededError just means that the response has taken more time
that the authorized deadline (60s), this could be due to several
reason ranging from slow application code loading, slow application
code execution, slow datastore queries to M/S latency issues.
I only suggered the latter because it is the most common, and
migrating to HRD would eliminate this possible cause.
If you are looking more operational support with a response SLA, we
are offering this as part of the premier accounts:
http://www.google.com/enterprise/cloud/appengine/pricing.html
Hope that helps.
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/UrfiFXjdiTcJ.
>
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
--
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations
Can you give us some indication if the migration tool is ever going to include blobstore migration? That's the only thing holding me back. I know I can do it myself but I'd rather not. I see now that it has gone ga, have you stuck a fork in it and called it done?
Thanks
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/f7KzNP-pCuwJ.
I've filed a bug against this documentation.
> It also says "queries on a single guestbook to be strongly consistent, but
> also limits changes to the guestbook to 1 write per second (the supported
> limit for entity groups). Therefore, writing to a single entity group per
> guestbook is not ideal when high usage is expected. If your app is likely to
> encounter heavy write usage, consider using another means. For example, you
> can put recent posts in memcache with an expiration, and then display a mix
> of recent posts from memcache and posts retrieved from the datastore."
> How could we trust by putting data to memcache if we know it can be evicted
> any time?
You wouldn't as definitive storage but it is reasonable to cache
recent posts there.
> To use HRD is not viable for applications which need strong
> consistency for high rate of puts.
You may have to think about how your organize your data in order to
satisfy your consistency and throughput requirements but I am very
skeptical when you say that it is simply not viable.
Google, for example, has been successful using the same technology for
many of its own high-volume properties.
> At the moment MS is perfect what it does
> but bloody thing keeps dying..
That is an architectural problem that is very hard to fix with making
the same kinds of trade-offs that we made when implementing HRD .
Cheers,
Brian
Probably not.
"Highly reliable" suggests that you synchronously replicate your data
across several machines and data centers (assuming that you want
consistency) but it is hard to make that "fast".
Cheers,
Brian
I'm getting tons of DeadlineExceededError since the maintenance last night too. It'll say in the log the requests are like 60 to 85 seconds and the same requests at other times go through in 200 milliseconds.Today I'm also getting a lot of "InternalError: internal error."
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/c0dV7sBY9jEJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Reminds me of the symptoms seen when we used M/S: suddenly a burst of
DEE and many instances gets killed, with these two logging messages:
I 2011-12-08 13:03:35.164
This request caused a new process to be started for your application,
and thus caused your application code to be loaded for the first time.
This request may thus take longer and use more CPU than a typical
request for your application.
W 2011-12-08 13:03:35.164
A serious problem was encountered with the process that handled this
request, causing it to exit. This is likely to cause a new process to
be used for the next request to your application. If you see this
message frequently, you may be throwing exceptions during the
initialization of your application. (Error code 104)
"The API call datastore_v3.Get() took too long to respond and was
cancelled."
so much for HR solving everything
and fwiw, I've also run up $100 in charges on an older M/S app (no
code changes in months) that gets maybe 1000 requests/day. Nearly
every other request is a DDE
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.