[DOCS-2535] Document problems with unique/dropDups indexes in the rolling index build Created: 15/Jan/14 Updated: 17/Feb/15 Resolved: 27/Jan/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 4 weeks ago |
| Description |
|
There are a number of potential issues that can occur if creating a unique index with dropDups on a collection in a rolling fashion in a replica set as documented in http://docs.mongodb.org/manual/tutorial/build-indexes-on-replica-sets/ We should document that this is not a good way to build a unique index and also document our suggestions for a unique index with dropDups on a replica set. |
| Comments |
| Comment by Githook User [ 22/Jan/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 22/Jan/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |