[DOCS-1871] Increase Clarification about Challenges of Renaming Config Servers Created: 30/Aug/13 Updated: 05/Mar/18 Resolved: 03/Sep/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Tang | Assignee: | Bob Grabar |
| 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, 24 weeks, 1 day ago | ||||||||
| Description |
|
Make clear on the deployment-related material that it's impossible to rename a cluster without downtime. Best practice is to use CNAMES and DNS to permit easy renumbering and naming of hosts. |
| Comments |
| Comment by auto [ 03/Sep/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 03/Sep/13 ] |
|
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> |