[SERVER-5686] Add write concern to copydb command Created: 23/Apr/12 Updated: 06/Dec/22 Resolved: 21/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Description |
|
There should be a way to specify a write concern to be used after every insert in a copydb command, otherwise it's possible to overrun replication on the destination set, causing the secondaries to be too stale to catch up. |
| Comments |
| Comment by Eric Milkie [ 21/Jun/18 ] |
|
copyDb command is deprecated and will be removed. |