Hi Vinny,

We do appreciate taking the time to go through our issue.

Haven't had the chance to download the log files yet. But in the console,
there is no sign at all about these tasks in the backend log files. Only
when we shut down the backend we see those commented errors.

We can't move the task execution to regular front instances as some of the
tasks take more than 10 minutes to be executed (these tasks are reports and
can really take very long). This is one of the queue configuration we are
having troubles with:

<queue>

 <name>scheduledReportsQueue</name>

 <rate>50/m</rate>

 <bucket-size>100</bucket-size>

 <max-concurrent-requests>2</max-concurrent-requests>

    <retry-parameters>

     <task-retry-limit>2</task-retry-limit>

       <task-age-limit>1h</task-age-limit>

    </retry-parameters>

</queue>
We are moving to HRD in the coming weeks. Hope the issue disappears after
the migration.

This backend we are having the issue is set as private. We are going to
make it public to see if there is any difference, and see what happens if
we make a regular HTTP request after it gets stuck.

Many thanks,
Luis



2013/10/10 Vinny P <vinny...@gmail.com>

> On Wed, Oct 9, 2013 at 2:55 AM, Luis <l.pereira.fernan...@gmail.com>
> wrote:
>
>> Basically we have a cron job which identifies certain heavy activities that 
>> need to be executed. The cron job sends these activities as tasks to a queue 
>> as a mean to have them executed in an ordered way in a dynamic backend.
>>
>>
>> The problem is that sometimes the tasks are never executed and the backend 
>> gets stuck or zombie. In the backend logs we see no evidence at all of the 
>> tasks (the actual request doesn't get recorded), even though according to 
>> the tasks queues console there should some of them running.
>>
>>
> It's odd that you're not seeing any error logs from the tasks. Are you
> sure you're seeing all the logs? If you download your logs, do you see any
> error logs pertaining to the backends there?
>
> Can you try moving the task queues to send requests to a front end
> instance and see if that works? What settings is each task configured with
> (for instance, the *retryoptions*)?
>
>
> On Wed, Oct 9, 2013 at 2:55 AM, Luis <l.pereira.fernan...@gmail.com>
>  wrote:
>
>> We are on Java and M/S. Have you ever faced something similar? Any ideas or 
>> suggestions to get rid of this issue?
>>
>>
>
> Try to migrate off M/S to the HRD datastore:
> https://developers.google.com/appengine/docs/adminconsole/migration
>
> M/S occasionally has weird, difficult-to-trace errors.
>
>
>
> -----------------
> -Vinny P
> Technology & Media Advisor
> Chicago, IL
>
> App Engine Code Samples: http://www.learntogoogleit.com
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/nMTnpLQiPEI/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to