Thanks Mickey.
Was this perhaps also a not-so-gentle push for us heavyweight Java M/S
guys to move our stuff to HRD and backends? ;)
Seriously though, I think I'm going to add the option in my app to
startup backend instance(s) that do something like this:
while (tasksAreSlackingOff() && haveMoreWork() &&
(!LifecycleManager.getInstance().isShuttingDown()) {
grabAJobToPickupSomeOfTheSlackFromThoseTaskSlackers();
saveState();
}
Better safe than sorry.
/Tom
On Jun 7, 4:32 am, "Mickey Kataria (Google Employee)"
<[email protected]> wrote:
> Update: There was an issue with how the app servers were throttling
> requests from task queues. It has only impacted Java apps running
> with the master/slave datastore. We've put in a temporary fix that
> alleviates the problem and will roll out a permanent fix in the next
> day or so.
>
> On Jun 7, 10:52 am, "Mickey Kataria (Google Employee)"
>
>
>
>
>
>
>
> <[email protected]> wrote:
> > We're aware there is an issue and are looking into it. I'll post an
> > update as I have more info.
>
> > On Jun 7, 8:30 am, John Wheeler <[email protected]> wrote:
>
> > > This may or may not be related, but we're getting
>
> > > ExclusiveLockError
> > > UnknownError
> > > and FinalizationError
>
> > > when using Mapreduce which uses the TQ heavily. We never encountered these
> > > errors before today which leads me to believe that the errors above are
> > > related.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
