[DOCS-1323] Document that Replica Set Names Must be Unique Created: 01/Apr/13  Updated: 26/Sep/13  Resolved: 25/Sep/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: David Hows Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 10 years, 20 weeks, 6 days ago

 Description   

We currently dont have a process for changing the name of a replica set.

Can we document the process so people are aware of whats involved.



 Comments   
Comment by auto [ 26/Sep/13 ]

Author:

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

Message: DOCS-1323: text update
Branch: master
https://github.com/mongodb/docs/commit/38f25410fc72733f03d55c2e75a3ec2566d634b6

Comment by auto [ 26/Sep/13 ]

Author:

{u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}

Message: DOCS-1323 replica set names must be unique

Signed-off-by: Sam Kleinman <samk@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/5fd5a7266ccc76f7cea8dc6f590ddd7060314cc6

Comment by David Hows [ 02/Apr/13 ]

Is this because they misconfigure two replica sets with the same name for some reason, and that caused some problem? If so, that is fine as long as they don't have members crossing between sets.

Yes, this is the scenario we need this documentation for. This was highlighted in the PHP case linked above.

This issue has come up once or twice out in stack overflow as well.

Comment by Scott Hernandez (Inactive) [ 02/Apr/13 ]

What case is this supposed to cover and what "recovery" was needed? Why would someone need to change the replica set name? Is this because they misconfigure two replica sets with the same name for some reason, and that caused some problem? If so, that is fine as long as they don't have members crossing between sets.

If this is related to shards in a sharded cluster then that might require other documentation.

Comment by David Hows [ 02/Apr/13 ]

Given that we dont have an automated method for this we need to provide a manual process to help people recover from this problem.

We also need to outline very clearly duplicate replica set names this will cause issues with drivers.

Comment by Scott Hernandez (Inactive) [ 01/Apr/13 ]

We don't support changing names – there is no feature nor support for it. Do you just want to state that?

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