[DOCS-1589] Document the impact of having a hidden node being stopped and restarted regularly Created: 10/Jun/13 Updated: 09/Sep/13 Resolved: 06/Sep/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Zack Brown |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 23 weeks, 5 days ago | ||||
| Description |
|
Many customers use hidden nodes for backup purposes. Often these backups can require that the node is offline while they are taken. We should make mention of backup nodes with, priority:0, hidden:true and votes:0 which makes a hidden node which can be shutdown and not be counted as part of a majority. |
| Comments |
| Comment by auto [ 06/Sep/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 06/Sep/13 ] |
|
Author: {u'username': u'Zackrobat', u'name': u'Zack Brown', u'email': u'zack.brown@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |