yup, normally wouldn't manually touch those operations in the task queue. just there were cases that there are some other problems in the task queues so we would like to manually purge the task queues (which purge those operations too), and that's why there are those zombie job left in this case.
just to see if there are any ways to 'properly clean' these zombie job entries (sure can again manually delete these entries on those map-reduce-create entities through datastore viewer, just afraid again without knowing all its flow, such manual intervention may create some other problems), although it's not big deal to have those zombie entries being shown for now - eric On 22 February 2011 14:16, David Mora <dla.m...@gmail.com> wrote: > i would not touch the task queues for such operations, tho. > > They are used by the map reduce when it calculates the shards for each > segment of the map (maps using the index, assigning segments to shards > - and the shards execute via task queue doing the reduce). > > Probably you have a zombie job that is waiting for a shard to write > into the datastore (these is how the shards communicate for some > information) > > Anyways, glad it worked for you :) > > On 21 February 2011 23:51, Eric Ka Ka Ng <ngk...@gmail.com> wrote: > > thx David! This is what i'm looking for! good reference! > > there were some mapreduce jobs (copy), which i believe its callback task > has > > been deleted from the taskqueues when i cleaned the queue, being stuck in > > the system and could not be aborted > > from http://{version}{host}/_ah/mapreduce (nothing changed after i click > > abort in the page) > > i know probably the jobs should no longer exist and it's just some task > > entries being left in the datastore. know any ways i could clean up those > > entries too? > > > > - eric > > > > On 22 February 2011 13:14, David Mora <dla.m...@gmail.com> wrote: > >> > >> is a mapreduce (just like the delete) > >> > >> you can access it thru: http://{version}{host}/_ah/mapreduce > >> > >> i think it has a callback that cleans up the job after it is > done/aborted > >> tho. > >> > >> On 21 February 2011 23:08, Tom Wu <service.g2...@gmail.com> wrote: > >> > +1 > >> > > >> > 2011/2/11 Eric Ka Ka Ng <ngk...@gmail.com> > >> >> > >> >> The new function to copy data from a GAE instance to another GAE > >> >> instance > >> >> makes some of our operations much more convenient! Thx for making > this > >> >> feature available! > >> >> I know this function is still experimental, I have a question in > using > >> >> this feature. > >> >> > >> >> After i have started a copy / delete task, there would be a link to > >> >> show > >> >> the current status of the task. however, if i leave the page and > later > >> >> open > >> >> the GAE admin console page, i couldn't find that link again and have > no > >> >> way > >> >> to go back to the screen which i can check current status of the > tasks. > >> >> (i > >> >> can see the operations' status from the datastore admin page, but i > >> >> can't > >> >> click to go to see the details) > >> >> > >> >> What's more, if there are any copy tasks fail for whatever reasons, I > >> >> have > >> >> no way to abort the task. I could manually purge the task queue to > stop > >> >> it, > >> >> but the operations entries would still be under the Operation's > status > >> >> which > >> >> cannot be removed. > >> >> so would there be any accessible UI that we could monitor status / > >> >> abort > >> >> these copy / delete tasks in datastore admin? > >> >> - eric > >> >> > >> >> -- > >> >> 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. > >> > > >> > >> > >> > >> -- > >> http://about.me/david.mora > >> > >> -- > >> 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. > >> > > > > > > > > -- > http://about.me/david.mora > -- 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.
