[SERVER-3529] Sharded map reduce using merge stalls recreating indexes on the output collection. Created: 03/Aug/11 Updated: 12/Jul/16 Resolved: 30/Aug/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce, Sharding |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | 1.8.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Antoine Girbal |
| Resolution: | Done | Votes: | 0 |
| Labels: | mapreduce, | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux x86_64 |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Steps to reproduce:
Results: The script will complete on the first run no problems. It will get stuck on the second run when the server is trying to recreate indexes on the output collection. The python script will eventually fail with the following assertion: failed: final reduce failed: { result: "results", assertion: "getMore: cursor didn't exist on server, possible restart or timeout?", assertionCode: 13127, errmsg: "db assertion failure", ok: 0.0 }Before the script fails db.currentOp() will show the following with the seconds climbing: { , Here's the sharding info: > db.printShardingStatus() shards: { "_id" : "repl0", "host" : "repl0/behackett-dt:29017" } { "_id" : "repl1", "host" : "repl1/behackett-dt:29020" }databases: { "_id" : "admin", "partitioned" : false, "primary" : "config" } { "_id" : "delicious", "partitioned" : true, "primary" : "repl0" } delicious.links chunks: |
| Comments |
| Comment by auto [ 30/Aug/11 ] |
|
Author: {u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}Message: |
| Comment by Eliot Horowitz (Inactive) [ 30/Aug/11 ] |
|
Ok - so can you apply patch on 1.8 |
| Comment by Antoine Girbal [ 30/Aug/11 ] |
|
issue does not exist in 2.0 line due to refactoring. |
| Comment by Eliot Horowitz (Inactive) [ 30/Aug/11 ] |
|
Can you confirm is this is an issue in 2.0 or only 1.8? |
| Comment by Antoine Girbal [ 17/Aug/11 ] |
|
diff that fixes 1.8 |
| Comment by Antoine Girbal [ 15/Aug/11 ] |
|
I have to confirm but I think this issue is only in 1.8. |
| Comment by Bernie Hackett [ 03/Aug/11 ] |
|
Probably obvious but you need pymongo to run the script. |