[SERVER-7466] Replication always failed Created: 25/Oct/12 Updated: 11/Jul/16 Resolved: 29/Oct/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Thomas Rosenblatt | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | bug, replicaset | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 12.04 64 bits x86 |
||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Operating System: | Linux | ||||
| Participants: | |||||
| Description |
|
Hello, I'm facing a big issue in my production environment. The failing happend on a collection named record, where indexes are defined below : , , nws_rs_1:PRIMARY> db.record.stats() , And the secondary always fails with message: This is a big issue since I can't set any replication mechanism ! Thank you for you help. Thomas. |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 26/Oct/12 ] |
|
Great, glad it worked out. Yes, you should have a unique _id index on every collection if you're using replication, because replication needs a way to uniquely identify each document. See the warning here: http://www.mongodb.org/display/DOCS/Capped+Collections#CappedCollections-UsageandRestrictions. |
| Comment by Thomas Rosenblatt [ 26/Oct/12 ] |
|
Hello Kristina, Well I finally found a workaround that seems to work. 30 minutes after, when secondary was really started and replica was fully set, I restarted all processes, and replication was working just fine ! I will not try 2.2.1 RC nor downgrading now that my production seems stable, I will first wait for stable 2.2.1 to try. Just for info : Are collection without _id index replicable ? Thank you, Thomas. |
| Comment by Kristina Chodorow (Inactive) [ 25/Oct/12 ] |
|
There were some issues in 2.2.0 with replication ( |