[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: File mongo-crash-log.log    
Issue Links:
Duplicate
duplicates SERVER-41213 Unique background index builds may pr... Closed
Operating System: ALL
Steps To Reproduce:
  1. Have an unique index on a field.
  2. Have multiple documents without that indexed field
  3. Make a query with { field: {$exists: false } }
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 SERVER-41213. It was resolved going forward in 4.0.10 but you will still need to rebuild the broken indexes. Can you please do so and let me know if you still see the problem?

Generated at Thu Feb 08 04:58:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.