[SERVER-5536] 2.0/2.1 sharded mapReduce compatibility Created: 06/Apr/12 Updated: 11/Jul/16 Resolved: 12/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Antoine Girbal |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Seems like there's an incompatibility between 2.0 mongod/2.1 mongos on sharded mapreduce. To repro, replace 2.1 mongod with 2.0.4 mongod and run features2.js, results in :
Attached sample output (there was some additional spurious logging in the mongos in this output, but reproducible in multiple other tests). |
| Comments |
| Comment by auto [ 12/Jun/12 ] | |||||||||||||||
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: | |||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 12/Jun/12 ] | |||||||||||||||
|
I have a fix for this. will commit in a minute. | |||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 12/Jun/12 ] | |||||||||||||||
|
tests failing | |||||||||||||||
| Comment by auto [ 12/Jun/12 ] | |||||||||||||||
|
Author: {u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}Message: | |||||||||||||||
| Comment by auto [ 12/Jun/12 ] | |||||||||||||||
|
Author: {u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}Message: | |||||||||||||||
| Comment by Antoine Girbal [ 07/Jun/12 ] | |||||||||||||||
|
In addition to "shards", the "shardedOutputCollection" field needs to be passed for compatibility. | |||||||||||||||
| Comment by Antoine Girbal [ 07/Jun/12 ] | |||||||||||||||
|
Problem is that mongod 2.0 expects a "shards" sub-object in the command, which infers the shards to pull from.
|