[google-appengine] Continued Random 500 Error
App Engine Staff, I continue to receive this error on all my apps. I receive this error on cold starts. I say this because in the past Google has responded this is due to > 1 sec averages, causing Google to not scale your app. This is not the case for me. I receive it on 0 load. I see these on 3 different apps, at random times. It is most annoying when I receive this error on my CRON entries. Obviously, this causes cron to be unreliable. To get around this I have had to add "warmup" cron entries 1 minute before my real cron entries. I feel it is ridiculous for me to have to do so. Please, can somebody respond on this issue? I see many others in the group reporting similar findings. To summarize, I understand this error can be a result of Google not scaling your app + too many requests and requests timing out in 10 second queue. This is not the case for my app. I receive it when my app has NO load. Request was aborted after waiting too long to attempt to service your request. This may happen sporadically when the App Engine serving cluster is under unexpectedly high or uneven load. If you see this message frequently, please contact the App Engine team. -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] app-id
You must use the specific email address to create the GAE app. If you own the gmail address you can create an app with the same name. If you delete the gmail account the name will be blocked forever. After you create the app you can add new administrators and delete the original one if you want. 2010/10/25 ach-nein : > > i'd like to set up an appspot app with a specific app-id which is to be > visible to end users. > for that purpose i need to have a certain id but GAE is telling me it's not > available. > I own this app-id as an gmail address, is it possible to verify that it's > mine, and be allowed to create such an app? > if not, is it possible to delete the email address and free up the name for > the app? > > -- > 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...@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-appeng...@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.
[google-appengine] app-id
i'd like to set up an appspot app with a specific app-id which is to be visible to end users. for that purpose i need to have a certain id but GAE is telling me it's not available. I own this app-id as an gmail address, is it possible to verify that it's mine, and be allowed to create such an app? if not, is it possible to delete the email address and free up the name for the app? -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: [appengine-java] Mapreduce gives error when I execute job on appengine cloud?
Have you created a descending index on the key of the entity group you try to map ? (required for mapreduce jobs) From: suersh babu Reply-To: Date: Fri, 22 Oct 2010 14:52:17 +0530 To: , Subject: [appengine-java] Mapreduce gives error when I execute job on appengine cloud? Hi, I am using mapreduce to run the job but when I try to run the job in mapreduce by clicking run button I am getting error like this : Error -- java.lang.RuntimeException: Full stack trace is available in the server logs. Message: Got an IOException while trying to make splits In my local machine mapreduce works fine, It executed the job without any error. I am using app engine sdk 1.3.8 Following is the server log generated by my application for the mapreduce error. 1. 10-22 02:02AM 49.783 2. com.google.appengine.tools.mapreduce.DatastoreInputFormat getSplits: Getting input splits for: Payment 3. 4. E 10-22 02:02AM 49.810 5. com.google.appengine.tools.mapreduce.MapReduceServlet handleCommand: Got exception while running command 6. java.lang.RuntimeException: Got an IOException while trying to make splits 7. at com.google.appengine.tools.mapreduce.MapReduceServlet.handleStart(MapReduceS ervlet.java:747) 8. at com.google.appengine.tools.mapreduce.MapReduceServlet.handleStartJob(MapRedu ceServlet.java:364) 9. at com.google.appengine.tools.mapreduce.MapReduceServlet.handleCommand(MapReduc eServlet.java:247) 10. at com.google.appengine.tools.mapreduce.MapReduceServlet.doPost(MapReduceServle t.java:184) 11. at javax.servlet.http.HttpServlet.service(HttpServlet.java:713) 12. at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) 13. at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) 14. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1166) 15. at com.veersoft.filter.ResetUserMessagesAndErrorsFilter.doFilter(ResetUserMessa gesAndErrorsFilter.java:28) 16. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1157) 17. at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlob UploadFilter.java:97) 18. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1157) 19. at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFi lter.java:35) 20. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1157) 21. at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(Transa ctionCleanupFilter.java:43) 22. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1157) 23. at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) 24. at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) 25. at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) 26. at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) 27. at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) 28. at com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHa ndlerMap.java:238) 29. at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) 30. at org.mortbay.jetty.Server.handle(Server.java:326) 31. at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) 32. at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnectio n.java:923) 33. at com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcReque stParser.java:76) 34. at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) 35. at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest (JettyServletEngineAdapter.java:135) 36. at com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java:261 ) 37. at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingReque st(RuntimePb.java:8486) 38. at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingReque st(RuntimePb.java:8484) 39. at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApp licationHandler.java:24) 40. at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:418) 41. at com.google.net.rpc.impl.Server$RpcTask.runInContext(Server.java:572) 42. at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java :448) 43. at com.google.tracing.TraceContext.runInContext(TraceContext.java:688) 44. at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedC ontextNoUnref(TraceContext.java:326) 45. at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedC ontext(TraceContext.java:318) 46. at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:4 46) 47. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11 10) 48. at java.util.concurrent.ThreadPoolEx
Re: [google-appengine] Does the task queue api not limited by the 30 seconds ?
Yes, the task-queue is also limited to 30 seconds. Longer running jobs are on the roadmap (http://code.google.com/appengine/docs/roadmap.html). The task queue is ''better'' than user requests when the request needs run multiple times to complete some processing, unless you client knows it needs to keep re-requesting. Of course in many cases a batch of tasks are initiated by a user request. Also, if a process takes a long time to run it should be in a task; otherwise your app may not get additional instances spun-up. I think it would be better to push the work from your render farm on EC2 to GAE when it is completed. Otherwise you will need to poll to find updates. Of course, if you only need updates once per hour polling is much less of a concern. Robert On Sun, Oct 24, 2010 at 09:37, Maxim Veksler wrote: > Hello, > Sorry for the basic question, can't find any clear answer on the subject. > Is the task queue API in any way better for long term running jobs then a > simple request to a defined "notfityUpdate" interface being called by our > processing farm? > While at it, what it the most recommended method for pushing data from the > rendering farm, sitting on EC2 to GAE datastore? > The GAE application is java if that plays any role, but don't let that stop > you. > Thanks, > Maxim. > > -- > 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...@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-appeng...@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.
Re: [google-appengine] Re: Fan-in with materialized views: A sketch
Hi Dmitry, Glad to hear it was helpful! Not sure when you checked it out last, but I made a number of good (I think) improvements in the last couple days, such as continuations to allow splitting large groups of work up. Robert On Sun, Oct 24, 2010 at 07:57, Dmitry wrote: > Robert, > > You grouping_with_date_rollup.py example was extremely helpful. Thanks > a lot again! :) > > On Oct 14, 8:47 pm, Robert Kluin wrote: >> Hey Carles, >> Glad it seems helpful. I am hoping to get time today to push out >> some revisions and sample code. >> >> Robert >> >> On Thu, Oct 14, 2010 at 05:50, Carles Gonzalez wrote: >> > Robert, I took a brief inspection at your code and seems very cool. Exactly >> > what i was lloking for for my report generation and such. >> > I'm looking forward for more examples, but it seems a very valuable >> > addition >> > for our toolbox. >> > Thanks a lot! >> >> > On Wed, Oct 13, 2010 at 9:20 PM, Carles Gonzalez >> > wrote: >> >> >> Neat! I'm going to see this code, hopefully I'll understand something :) >> >> On Wednesday, October 13, 2010, Robert Kluin >> >> wrote: >> >> > Hey Dmitry, >> >> > In case it might help, I pushed some code to bitbucket. At the >> >> > moment I would (personally) say the code is not too pretty, but it >> >> > works well. :) >> >> > http://bitbucket.org/thebobert/slagg >> >> >> > Sorry it does not really have good documentation at the moment, but >> >> > I think the basic example I threw together will give you a good idea >> >> > of how to use it. I need to do another cleanup pass over the API to >> >> > make a few more refinements. >> >> >> > I pulled this code out of one of my apps, and tried to quickly >> >> > refactor it to be a bit more generic. We are currently using >> >> > basically the same code in three apps to do some really complex >> >> > calculations. As soon as I get time I will get an example up showing >> >> > how to use it for neat stuff, like overall, yearly, monthly, and daily >> >> > aggregates across multiple values (like total dollars and quantity). >> >> > The cool thing is that you can do all of those aggregations across >> >> > various groupings, like customer, company, contact, and sales-person, >> >> > at once. I'll get that code pushed out in the next few days. >> >> >> > Would love to get some feedback on it. >> >> >> > Robert >> >> >> > On Tue, Oct 12, 2010 at 17:26, Dmitry wrote: >> >> >> Ben, thanks for your code! I'm trying to understand all this stuff >> >> >> too... >> >> >> Robert, any success with your "library"? May be you've already done >> >> >> all stuff we are trying to implement... >> >> >> >> p.s. where is Brett S.:) would like to hear his comments on this >> >> >> >> On Sep 21, 1:49 pm, Ben wrote: >> >> >>> Thanks for your insights. I would love feedback on this implementation >> >> >>> (Brett S. suggested we send in our code for >> >> >>> this)http://pastebin.com/3pUhFdk8 >> >> >> >>> This implementation is for just one materialized view row at a time >> >> >>> (e.g. a simple counter, no presence markers). Hopefully putting an ETA >> >> >>> on the transactional task will relieve the write pressure, since >> >> >>> usually it should be an old update with an out-of-date sequence number >> >> >>> and be discarded (the update having already been completed in batch by >> >> >>> the fork-join-queue). >> >> >> >>> I'd love to generalize this to do more than one materialized view row >> >> >>> but thought I'd get feedback first. >> >> >> >>> Thanks, >> >> >>> Ben >> >> >> >>> On Sep 17, 7:30 am, Robert Kluin wrote: >> >> >> >>> > Responses inline. >> >> >> >>> > On Thu, Sep 16, 2010 at 17:32, Ben >> >> >>> > wrote: >> >> >>> > > I have a question about Brett Slatkin's talk at I/O 2010 on data >> >> >>> > > pipelines. The question is about slide #67 of his pdf, >> >> >>> > > corresponding >> >> >>> > > to minute 51:30 of his talk >> >> >> >>> > > >http://code.google.com/events/io/2010/sessions/high-throughput-data-p... >> >> >> >>> > > I am wondering what is supposed to happen in the transactional >> >> >>> > > task >> >> >>> > > (bullet point 2c). Would these updates to the materialized view >> >> >>> > > cause >> >> >>> > > you to write too frequently to the entity group containing the >> >> >>> > > materialized view? >> >> >> >>> > I think there are really two different approaches you can use to >> >> >>> > insert your work models. >> >> >>> > 1) The work models get added to the original entity's group. So, >> >> >>> > inside of the original transaction you do not write to the entity >> >> >>> > group containing the materialized view -- so no contention on it. >> >> >>> > Commit the transaction and proceed to step 3. >> >> >>> > 2) You kick off a transactional task to insert the work model, or >> >> >>> > fan-out more tasks to create work models :). Then you proceed to >> >> >>> > step 3. >> >> >> >>> > You can use method 1 if you have only a few aggregates. If you have
[google-appengine] Re: Urgent Help
Sorry, solved. Thanks. 2010/10/24 Massimiliano > Dear All, > I have created an application and offline it's working well. > The app.yalm is: > > application: prova > version: prima > runtime: python > api_version: 1 > > handlers: > - url: /static > static_dir: static > > - url: /.* > script: main.py > > When I try to change the application name with "fanpagemax" the name of the > appspot, the application stops working and if I deploy it, the application > doesn't work too. > Please help me, I can't understand and I have worked a lot on this > application. > > Thanks > > Max > > -- > > My email: massimiliano.pietr...@gmail.com > My Google Wave: massimiliano.pietr...@googlewave.com > -- My email: massimiliano.pietr...@gmail.com My Google Wave: massimiliano.pietr...@googlewave.com -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Urgent Help
Dear All, I have created an application and offline it's working well. The app.yalm is: application: prova version: prima runtime: python api_version: 1 handlers: - url: /static static_dir: static - url: /.* script: main.py When I try to change the application name with "fanpagemax" the name of the appspot, the application stops working and if I deploy it, the application doesn't work too. Please help me, I can't understand and I have worked a lot on this application. Thanks Max -- My email: massimiliano.pietr...@gmail.com My Google Wave: massimiliano.pietr...@googlewave.com -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Does the task queue api not limited by the 30 seconds ?
Hello, Sorry for the basic question, can't find any clear answer on the subject. Is the task queue API in any way better for long term running jobs then a simple request to a defined "notfityUpdate" interface being called by our processing farm? While at it, what it the most recommended method for pushing data from the rendering farm, sitting on EC2 to GAE datastore? The GAE application is java if that plays any role, but don't let that stop you. Thanks, Maxim. -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: App engine down time or problem with CRON requests
Ok thanks for confirming you saw this as well. Looks like the same thing occured today, same time frame as before. Chris On Oct 22, 11:02 pm, sodso wrote: > Yes, same happened for me as well, looks like CRON jobs arent > reliable, so i have decided to implement double-checking logic to > check whether the job has run or not by using a datatstore / memcache > record > > On Oct 22, 7:51 pm, Chris Prinos wrote: > > > > > > > > > Anyone know if there was scheduled down time 10/22/2010 around 12:30AM > > PDT? > > > None of my cron-initiated requests were triggered from about 12:33 AM > > PDT to 1:05 AM PDT, but there were no errors in the logs. -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Fan-in with materialized views: A sketch
Robert, You grouping_with_date_rollup.py example was extremely helpful. Thanks a lot again! :) On Oct 14, 8:47 pm, Robert Kluin wrote: > Hey Carles, > Glad it seems helpful. I am hoping to get time today to push out > some revisions and sample code. > > Robert > > On Thu, Oct 14, 2010 at 05:50, Carles Gonzalez wrote: > > Robert, I took a brief inspection at your code and seems very cool. Exactly > > what i was lloking for for my report generation and such. > > I'm looking forward for more examples, but it seems a very valuable addition > > for our toolbox. > > Thanks a lot! > > > On Wed, Oct 13, 2010 at 9:20 PM, Carles Gonzalez wrote: > > >> Neat! I'm going to see this code, hopefully I'll understand something :) > >> On Wednesday, October 13, 2010, Robert Kluin > >> wrote: > >> > Hey Dmitry, > >> > In case it might help, I pushed some code to bitbucket. At the > >> > moment I would (personally) say the code is not too pretty, but it > >> > works well. :) > >> > http://bitbucket.org/thebobert/slagg > > >> > Sorry it does not really have good documentation at the moment, but > >> > I think the basic example I threw together will give you a good idea > >> > of how to use it. I need to do another cleanup pass over the API to > >> > make a few more refinements. > > >> > I pulled this code out of one of my apps, and tried to quickly > >> > refactor it to be a bit more generic. We are currently using > >> > basically the same code in three apps to do some really complex > >> > calculations. As soon as I get time I will get an example up showing > >> > how to use it for neat stuff, like overall, yearly, monthly, and daily > >> > aggregates across multiple values (like total dollars and quantity). > >> > The cool thing is that you can do all of those aggregations across > >> > various groupings, like customer, company, contact, and sales-person, > >> > at once. I'll get that code pushed out in the next few days. > > >> > Would love to get some feedback on it. > > >> > Robert > > >> > On Tue, Oct 12, 2010 at 17:26, Dmitry wrote: > >> >> Ben, thanks for your code! I'm trying to understand all this stuff > >> >> too... > >> >> Robert, any success with your "library"? May be you've already done > >> >> all stuff we are trying to implement... > > >> >> p.s. where is Brett S.:) would like to hear his comments on this > > >> >> On Sep 21, 1:49 pm, Ben wrote: > >> >>> Thanks for your insights. I would love feedback on this implementation > >> >>> (Brett S. suggested we send in our code for > >> >>> this)http://pastebin.com/3pUhFdk8 > > >> >>> This implementation is for just one materialized view row at a time > >> >>> (e.g. a simple counter, no presence markers). Hopefully putting an ETA > >> >>> on the transactional task will relieve the write pressure, since > >> >>> usually it should be an old update with an out-of-date sequence number > >> >>> and be discarded (the update having already been completed in batch by > >> >>> the fork-join-queue). > > >> >>> I'd love to generalize this to do more than one materialized view row > >> >>> but thought I'd get feedback first. > > >> >>> Thanks, > >> >>> Ben > > >> >>> On Sep 17, 7:30 am, Robert Kluin wrote: > > >> >>> > Responses inline. > > >> >>> > On Thu, Sep 16, 2010 at 17:32, Ben > >> >>> > wrote: > >> >>> > > I have a question about Brett Slatkin's talk at I/O 2010 on data > >> >>> > > pipelines. The question is about slide #67 of his pdf, > >> >>> > > corresponding > >> >>> > > to minute 51:30 of his talk > > >> >>> > > >http://code.google.com/events/io/2010/sessions/high-throughput-data-p... > > >> >>> > > I am wondering what is supposed to happen in the transactional > >> >>> > > task > >> >>> > > (bullet point 2c). Would these updates to the materialized view > >> >>> > > cause > >> >>> > > you to write too frequently to the entity group containing the > >> >>> > > materialized view? > > >> >>> > I think there are really two different approaches you can use to > >> >>> > insert your work models. > >> >>> > 1) The work models get added to the original entity's group. So, > >> >>> > inside of the original transaction you do not write to the entity > >> >>> > group containing the materialized view -- so no contention on it. > >> >>> > Commit the transaction and proceed to step 3. > >> >>> > 2) You kick off a transactional task to insert the work model, or > >> >>> > fan-out more tasks to create work models :). Then you proceed to > >> >>> > step 3. > > >> >>> > You can use method 1 if you have only a few aggregates. If you have > >> >>> > more aggregates use the second method. I have a "library" I am > >> >>> > almost > >> >>> > ready to open source that makes method 2 really easy, so you can > >> >>> > have > >> >>> > lots of aggregates. I'll post to this group when I release it. > > >> >>> > > And a related question, what happens if there is a failure just > >> >>> > > after > >> >>> > > the transaction in bullet #2, but rig
Re: [google-appengine] MapReduce - Map task time limit - Is it 30 seconds?
Yes, I think so. But each task only handle one entity, it almost won't exceed 30 seconds to process it. -- keakon 2010/10/24 Jaganathan (ஜ௧நாதன்) : > Hi > Just curious and want to confirm the following. > In MapReduce (http://code.google.com/p/appengine-mapreduce/), should any > single map task *still* run within the 30 seconds limit? > Thanks > Jagan > -- > Let the words of our mouth and the meditations of our heart > Be acceptable in Thy sight here tonight! > - Rivers of Babylon (album) > > -- > 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...@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-appeng...@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.
[google-appengine] MapReduce - Map task time limit - Is it 30 seconds?
Hi Just curious and want to confirm the following. In MapReduce (http://code.google.com/p/appengine-mapreduce/), should any single map task *still* run within the 30 seconds limit? Thanks Jagan -- Let the words of our mouth and the meditations of our heart Be acceptable in Thy sight here tonight! - Rivers of Babylon (album) -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.