[SERVER-2117] Temporary MR collections don't get removed from all shards Created: 18/Nov/10 Updated: 18/Nov/10 Resolved: 18/Nov/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.6.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Giri Iyengar | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 64 bit, Amazon EC2 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
When you run many Map/Reduce jobs on a sharded environment, and explicitly call a drop collection in your code it seems that the mongos process sends the dropCollection call but it is not always executed by the shard server. Eventually we get a runtime exception when we go over the namespace limit for collections. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 18/Nov/10 ] |