[SERVER-12613] Find query using $or causing mongod memory footprint to balloon (Index Related) Created: 04/Feb/14 Updated: 11/Jul/16 Resolved: 06/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | 2.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brad C. | Assignee: | hari.khalsa@10gen.com |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 6.5 x86_64 (connected through mongos but DB hosted on primary shard) |
||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | See file. |
| Participants: |
| Description |
|
See the attached file which should reproduce the issue. (Or it did on the two systems I tried it on.) |
| Comments |
| Comment by Githook User [ 06/Feb/14 ] |
|
Author: {u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}Message: |
| Comment by hari.khalsa@10gen.com [ 05/Feb/14 ] |
|
Thanks for posting this, Brad! I will submit a fix in the next day or two. Please do keep testing 2.5.5 and any extreme query-related behavior |
| Comment by Daniel Pasette (Inactive) [ 05/Feb/14 ] |
|
Thanks for the report Brad. |