[SERVER-18472] Query Exception: Assertion: 13548:BufBuilder attempted to grow() to 134217728 bytes, past the 64MB limit. Created: 14/May/15 Updated: 16/Nov/21 Resolved: 29/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Stefan Seiffarth [X] | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 64bit, MongoDB 3.0.2/3.0.3 |
||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Steps to reproduce:
Actual result:
Expected result: Background: That's why I'm building a very long query which looks like this {id=id1, revision=revision1}or ... or {id=id1000, revision=revision1000}to see if if my current documents are actually still in the collection and are not updated for unknown reasons. If this is the wrong category for this bug, please move it accordingly, I imagine it might be a bug in the core project, but my reproduction is in C# that's why I created it for the C# driver. |
| Comments |
| Comment by Ramon Fernandez Marina [ 29/Oct/15 ] | ||||||||||||||
|
I'm not able to reproduce this behavior in the master branch starting with version 3.1.1; here's the repro I've been using:
Users affected by this issue may want to download the latest 3.2 release candidate and check that their workloads no longer trigger the 64MB limit. Regards, | ||||||||||||||
| Comment by Ed Ivanushkin [ 29/Oct/15 ] | ||||||||||||||
|
Seems like this issue is there for awhile. Previously, trying to do aggregation of large scale would just bring server down. Now server sustains but client doesn't get results. Are there any plans to fix this permanently? 64Mb is not that much considering amount of data aggregation can produce. | ||||||||||||||
| Comment by Craig Wilson [ 14/May/15 ] | ||||||||||||||
|
Hi Steffan, I've moved this to the SERVER group as this appears to be an issue on that end. They might come back and ask for more information. Craig |