Thanks for the report (and the patch!). On Thu, Jan 3, 2013 at 1:31 PM, Jason Collins <[email protected]>wrote:
> I found the bug that leads to this in the mapreduce framework. The patch > to fix is attached to the issue: > http://code.google.com/p/appengine-mapreduce/issues/detail?id=154 > > > On Thursday, 20 December 2012 15:34:52 UTC-6, Jason Collins wrote: >> >> We are using the "legacy" (non-PipelineAPI) version of the mapreduce >> library: >> http://code.google.com/p/**appengine-mapreduce/<http://code.google.com/p/appengine-mapreduce/> >> >> The issue is that we can only ever get one shard processing, even for >> kinds that have >150,000 entities. We have tried different shard_count >> configurations, e.g, 4, 16, 128, but always only one shard processing >> entire dataset, which is very slow. >> >> I feel like I've missed a step (e.g., creating an index or something). >> >> Crossing my fingers that someone knows an offhand answer. >> >> Thanks, >> j >> > -- > 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/-/_anjmdcsBXgJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Johan Euphrosine (proppy) Developer Programs Engineer Google Developer Relations -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
