Timeline for MongoDB Replica Set member cannot start due "84 key/value already in index"
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 9, 2018 at 13:20 | vote | accept | Vinicius Deschamps | ||
| Apr 7, 2018 at 13:56 | history | edited | Md Haidar Ali Khan | CC BY-SA 3.0 |
correction of spelling of dbpath
|
| Apr 7, 2018 at 7:16 | comment | added | JJussi | Probably, after initial sync, you will never see it again... If your hardware works fine. | |
| Apr 6, 2018 at 12:50 | comment | added | Vinicius Deschamps | At least a way to avoid? | |
| Apr 6, 2018 at 11:02 | comment | added | JJussi | That is probably impossible... This is situation what should not exists. Log files may or may not have information about when and how this situation has developed. | |
| Apr 6, 2018 at 9:37 | comment | added | Vinicius Deschamps | Is it possible to know why this happened? | |
| Apr 5, 2018 at 17:27 | history | answered | JJussi | CC BY-SA 3.0 |