I'm able to direct tasks to the backends using the *target* arg as in
your example. And the backend state is 'start' when you're trying this?
Are you directing toward a specific backend instance (/N.backend_name/)
or just to /backend_name/? I am doing the latter.
Steve
On 11-09-09 05:00 PM, Rishi Arora wrote:
Thanks. Yes that worked for me. It just seems that backend
documentation isn't very intuitive. I couldn't tell from any of the
online docs that simply adding a backend to backends.yaml won't
configure a backend for you. It won't show up in the backends section
of the admin console until you execute appcfg.py update backends.
Another non-intuitive behavior - probably only for dynamic backends.
The admin console has a start/stop button. But obviously, if you hit
start, the dynamic backend won't actually start. That's clear from
the documentation. But, if you hit "stop", it almost looks like that
the backend is made inaccessbile. It won't process requests, and it
won't automatically restart on the next request. You have to hit the
"start" button first. I think for dynamic backends that button should
read "enable/disable".
Now the next thing I'm trying to get to work is sending a backend a
request from a task queue. I'm using the default task queue to do
this, and simply doing this doesn't work (a front-end instance
processes the taskqueue request):
taskqueue.add(url=[relative path to request handler], method='POST',
target=[backend name from app.yaml])
Modifying the above statement to specify the entire URL for the
backend in the "target" parameter does not help either - the taskqueue
request is still processed by a front-end instance. I also tried just
getting rid of the "target" parameter, and specifying the entire url
in the "url" parameter i.e.
url='https://backend.appid.appspot.com/path/to/requesthandler'. And
even that did not help. I fear forcing backends to process cron
entries defined with a full URL like above won't do the trick either.
So is there no way to force a backend to process a request?
On Fri, Sep 9, 2011 at 3:45 PM, Steve Sherrie <st...@wasteofpaper.com
<mailto:st...@wasteofpaper.com>> wrote:
Also, you can do...
*
*
*appcfg.py update **--backends your_app*
*
*
*
*
Steve
--
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/-/gvpp7TaOlykJ.
To post to this group, send email to
google-appengine@googlegroups.com
<mailto:google-appengine@googlegroups.com>.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
<mailto:google-appengine%2bunsubscr...@googlegroups.com>.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
--
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-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
--
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-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
