[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: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
We have a mongodb instance 3.2.10 running on machine with 4gb ram. This prevents us from using the textual indexing feature in production. |
| 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, |
| 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, |