[SERVER-4547] Disable full restore of sharded cluster Created: 22/Dec/11 Updated: 11/Jul/16 Resolved: 22/Dec/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Currently mongorestore doesn't intelligently handle restoring to a sharded cluster. This can cause bad things to happen to your cluster if you do this by accident. |
| Comments |
| Comment by auto [ 29/May/12 ] |
|
Author: {u'login': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}Message: Don't allow full mongorestore on sharded cluster. |
| Comment by auto [ 20/Jan/12 ] |
|
Author: {u'login': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}Message: Don't allow full mongorestore on sharded cluster. |
| Comment by Spencer Brody (Inactive) [ 22/Dec/11 ] |
|
https://github.com/stbrody/mongo/commit/d502bf9134cf2d8ab8cc490edda536da17b81723 waiting to be backported into 2.0 branch. |