[DOCS-7410] Document mongodump behaviour when connecting to a replica set Created: 14/Mar/16 Updated: 30/Oct/23 Resolved: 12/Aug/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | tools |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Adistambha | Assignee: | Steve Renaker (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 26 weeks, 5 days ago | ||||||||
| Description |
|
DOCS-6368 requests to document that mongodump will dump from a secondary node in a replica set by default. This behaviour is now changed in the latest version (3.2.4), where it will dump from the nearest node instead. Please see https://github.com/mongodb/mongo-tools/blob/r3.2.4/mongodump/mongodump.go#L131 |
| Comments |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |