[DOCS-2485] Backup of a sharded cluster should not require config server shutdown Created: 07/Jan/14 Updated: 17/Feb/15 Resolved: 05/Mar/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Osmar Olivo | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint-rollover | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 50 weeks ago |
| Description |
|
When describing the steps for backing up a sharded cluster, we mention that turning off one of the config servers prior to a mongodump is the best practice. In fact there isn't really a need to shutdown a config server as long as the balancer is disabled. Turning on and off of config servers can cause other issues in the cluster regarding balancing and availability. Currently i can find this being stated at http://docs.mongodb.org/manual/tutorial/backup-sharded-cluster-with-filesystem-snapshots/ But I suspect it may be rolling around in multiple places as well. |
| Comments |
| Comment by Githook User [ 05/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 05/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 05/Mar/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |
| Comment by Githook User [ 05/Mar/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |
| Comment by Scott Hernandez (Inactive) [ 04/Feb/14 ] |
|
Compared to other options doing a shutdown of the 2/3rd config server was the best suggestion. Using fsync+lock has serious issues. Disabling the balancer is not sufficient to freeze the metadata for all versions to take the backup. |