[DOCS-3891] BRS: Document what clustershot warnings mean and adjust any existing documentation regarding cluster snapshots Created: 11/Aug/14 Updated: 16/Mar/15 Resolved: 25/Aug/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Steve Briskin (Inactive) | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 24 weeks, 1 day ago |
| Description |
|
As part of BRS-1553, we will start taking cluster snapshots regardless of whether the balancer was stopped. There will be additional terse warnings in the UI and we need docs to better explain the state of the clustershots as well as the risks of restoring them. 1. Clustershot taken with the balancer running: The agent timed out waiting for the balancer to stop or current migrations to complete. Snapshots were taken and the clustershot is restorable. Possible data loss or orphan data if the clustershot is restored. Individual shards are restorable as normal. 2. Clustershot taken with 1 or more shards/config servers unreachable. The agent couldn't reach one of the shards/config server to insert a synchronization oplog token. Clustershot is not restorable, but the shards that succeeded were snapshotted and are restorable. See https://github.com/10gen/mms/pull/2184 and https://github.com/10gen/mms/pull/2262 for screenshots. This is scheduled for Aug 19th release. CC chunming.li, cailin.nelson@10gen.com |
| Comments |
| Comment by Githook User [ 02/Sep/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |
| Comment by Githook User [ 02/Sep/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |
| Comment by Githook User [ 02/Sep/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |
| Comment by Githook User [ 27/Aug/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |
| Comment by Githook User [ 27/Aug/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |
| Comment by Githook User [ 27/Aug/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |
| Comment by Steve Briskin (Inactive) [ 18/Aug/14 ] |
|
No. This change only covers clustershots. Checkpoints will required the balancer to be stopped and all shards to be reachable. |