[SERVER-34335] MongoDB Replica Set member cannot start "84 key/value already in index" Created: 05/Apr/18 Updated: 24/Apr/18 Resolved: 09/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Vinicius Deschamps | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi, I have a Replica Set with 3 members (1 primary and 2 secondaries), and one of the secondaries was working just fine and thrown the following error
After that the MongoDB cannot start anymore, and keep throwing the same error! How can I determine the root cause of it? Is there a way to prevent? How to solve it? |
| Comments |
| Comment by Ramon Fernandez Marina [ 09/Apr/18 ] |
|
vdeschamps, if I remember correctly, this error is triggered when the secondary is trying to index a document that's already present in the index; determining how this happened may not be feasible, so my recommendation would be to resync this node from a healthy one. Note that the MongoDB version you're running is very old and no longer supported, so I'd recommend you upgrade to the newest version (3.6) at your earliest convenience. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. Regards, |