legacy mapreduce library only running one shard

[Jason Collins]

We are using the "legacy" (non-PipelineAPI) version of the mapreduce library: 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

[Jason Collins]

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

[Johan Euphrosine]

Thanks for the report (and the patch!).

--
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 google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
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

[Xiaolong Cheng]

This is suddenly happening to me, since Jan 2018.  May I know what had been done to fix the issue? The original link is broken.