+1 I am seeing the same pre-SDk 1.4 behavior -- 20 sec backoffs.
What am I doing wrong?
My queue.yaml
queue:
- name: default
rate: 20/s
bucket_size: 100
retry_parameters:
task_age_limit: 120s
min_backoff_seconds: 1
max_backoff_seconds: 7
On Dec 7, 7:02 pm, Jason Collins w
Bump.
GAE team can you comment please?
--
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-appeng...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googl
Hi Jason,
Are you seeing this behavior in production or in the development
server?
On Dec 8, 2:02 pm, Jason Collins wrote:
> Has anyone had any luck getting max_backoff_seconds (in
> TaskRetryOptions) to work?
>
> I'm setting mine to 1,2,3 (seconds), but it seems to be on a 20s fixed
> retry sch
I am seeing this behavior in production. Will post logs tonight.
--
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-appeng...@googlegroups.com.
To unsubscribe from this group, send email to
google-a
Production.
On Dec 14, 8:23 pm, "Greg (Google)" wrote:
> Hi Jason,
>
> Are you seeing this behavior in production or in the development
> server?
>
> On Dec 8, 2:02 pm, Jason Collins wrote:
>
>
>
> > Has anyone had any luck getting max_backoff_seconds (in
> > TaskRetryOptions) to work?
>
> > I'm
Hello Jason, Vlad,
Our task scheduling is best effort. Although we try to schedule tasks
as nearly as possible to their etas, we don't guarantee that your
tasks will run at the exact time. Some delay is inevitable.
Cheers,
Nick Verne
On Dec 16, 10:21 am, Jason Collins wrote:
> Production.
>
>
Hi Nick,
Task schedule delays (best effort) are expected but this is not the case.
Take a look at the log excerpt below which shows a task with 6 reties.
Retries are perfectly timed on flat 20sec back off schedule. In other words
I have never seen task reties follow what I put in my queue.yaml.
Nick,
Your edge case definitely confused at least 2 of us. I imagine that
people will often be testing their queues on a low volume queue
initially. You might want to put something in the documentation, or at
least the code.
j
On Dec 16, 4:59 pm, Nicholas Verne wrote:
> Vlad,
>
> Your case is a
Vlad,
Your case is a bit of an edge case for us. At the time your task is
dispatched, do you have any other tasks still in the queue scheduled
to execute within the next twenty seconds? If not, your queue is
considered empty and will next be checked for tasks to dispatch in
twenty seconds time. If
Thanks Nick. That makes sense. Indeed, I have been running a single task
chain which would result in at most 1 task being pending at a time.
--
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-appeng
10 matches
Mail list logo
