[SERVER-3115] Incremental collection of map reduce should not be replicated Created: 18/May/11 Updated: 12/Jul/16 Resolved: 27/Jun/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Antoine Girbal | Assignee: | Antoine Girbal |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
It seems that inc collection is replicated according to |
| Comments |
| Comment by Sean Fannan [ 22/Jul/11 ] |
|
The issue though is that the creation and deletion of these tmp tables is written to the oplog so when you add a new member to the replica set, the recovery period takes way longer than it should. Any ideas if there is a way to avoid writing to the oplog, if there is just a way to ignore any tmp collections when syncing? My issue is that I have a map reduce function that is run every 30 minutes, so obviously after this script in existence for several months, thousands of tmp collections have been created. So when I bootup a new member of the replica set, it takes way longer than it should to recover. |
| Comment by Antoine Girbal [ 27/Jun/11 ] |
|
this is actually a non issue. |