[SERVER-41803] Standalone server crash with 'Unique index cursor seeing multiple records for key { : null } ' Created: 18/Jun/19 Updated: 18/Jun/19 Resolved: 18/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 4.0.4, 4.0.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Lauri Hälinen | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Mongo server crashes when it sees multiple records for key 'null' in an unique index. It won't restart unless the systemd service has endless respawn configured. |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 18/Jun/19 ] |
|
Glad to hear it! I'll close this ticket as a duplicate but please let us know if you see the issue again. |
| Comment by Lauri Hälinen [ 18/Jun/19 ] |
|
I actually already rebuilt the indexes and removed all the documents without the indexed fields. After that the server did not crash with the specified query. Good to know that it's been fixed already. |
| Comment by Danny Hatcher (Inactive) [ 18/Jun/19 ] |
|
It is likely that you are encountering |