[DOCS-4157] Improvements to "Enable Authentication in a Sharded Cluster" page Created: 09/Oct/14  Updated: 11/Nov/14  Resolved: 11/Nov/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-2.6, mongodb-3.0
Fix Version/s: v1.3.14

Type: Improvement Priority: Major - P3
Reporter: Luke Lovett Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 9 years, 14 weeks, 1 day ago

 Description   

http://docs.mongodb.org/manual/tutorial/enable-authentication-in-sharded-cluster/

1. The current page doesn't make it clear that downtime is required when "upgrading" a sharded cluster to use auth. It seems that other users have been confused by this as well and have asked about it on mongodb user.

2. The response to this question on GG also brings up considerations the documentation does not mention. Stopping 1 config server to ensure that metadata becomes read-only before stopping shard servers and stopping the balancer to ensure that documents are not in flight should become "step 2" of the process, or get merged into the current "step 2."



 Comments   
Comment by Githook User [ 11/Nov/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4157: adding clarification about downtime for auth conversions
Branch: master
https://github.com/mongodb/docs/commit/277bea84878f42eae0b2b2c31f1bacf14db23d99

Generated at Thu Feb 08 07:47:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.