[SERVER-26616] mongo out of memory on textual query Created: 13/Oct/16  Updated: 27/Oct/16  Resolved: 27/Oct/16

Status: Closed
Project: Core Server
Component/s: Querying, Text Search
Affects Version/s: 3.2.10
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Michael Dikman Assignee: Kelsey Schubert
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

mongo on aws docker instance. t2 medium machine


Attachments: File metrics.2016-10-13T14-05-40Z-00000     File metrics.2016-10-13T14-08-04Z-00000     Text File mongo-crash.txt     Text File mongo.log    
Issue Links:
Duplicate
duplicates SERVER-26534 Text search uses excessive memory Backlog
Operating System: ALL
Participants:

 Description   

We have a mongodb instance 3.2.10 running on machine with 4gb ram.
I created 700k documents with the string X in them (X is of length 6 character).
When i run textual query of the type:
db.MyCollection.find({$text: {$search: 'X'}})
We see that the memory raises by 800mb.
After running such a query 3-4 consequential times the mongodb instance is automatically restarted.

This prevents us from using the textual indexing feature in production.
Any workaround? Can we disable the query cache for such queries?



 Comments   
Comment by Kelsey Schubert [ 27/Oct/16 ]

Hi archmisha,

Thank you for providing the diagnostic.data and logs. I've examined the files and confirmed that you are encountering SERVER-26534, which is actively being investigated. Please feel free to vote for SERVER-26534 and watch it for updates.

Thanks again,
Thomas

Comment by Michael Dikman [ 27/Oct/16 ]

attached the required files

Comment by Ramon Fernandez Marina [ 14/Oct/16 ]

archmisha, this could be the same as SERVER-26534, which unfortunately, is still unresolved.

Can you please upload the contents of the diagnostic.data directory for the affected node? The logs from the last restart until you get the "out of memory" message will be helpful as well to determine if you're running into SERVER-26534 or if you've found something else.

Thanks,
Ramón.

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