[DOCS-7771] "Backup a Small Sharded Cluster with mongodump" contains an obsolete warning Created: 28/Apr/16 Updated: 11/Jan/17 Resolved: 28/Apr/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sylvain Chambon | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 41 weeks, 2 days ago |
| Description |
|
This page: https://docs.mongodb.org/manual/tutorial/backup-small-sharded-cluster-with-mongodump/ contains the following warning: "By default mongodump issue its queries to the non-primary nodes." However since 3.2 this is no longer the case: when connecting to a mongos or a replica set, mongodump connects to a primary by default (see commit 8fc478259d75235f96ae31fe271bf05f118fa98b linked to |
| Comments |
| Comment by Githook User [ 02/May/16 ] |
|
Author: {u'username': u'rkumar-mongo', u'name': u'ravind', u'email': u'ravind.kumar@10gen.com'}Message: /tutorial/backup-small-sharded-cluster-with-mongodump Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Ravind Kumar (Inactive) [ 28/Apr/16 ] |