[SERVER-35641] $FACET throws "BufBuilder attempted to grow()" while Created: 18/Jun/18 Updated: 18/Jun/18 Resolved: 18/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.15 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Janos Brezniczky | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | (The original code is NDA. I expect this bug fairly easy to reproduce.) |
||||||||
| Participants: | |||||||||
| Description |
|
I get a "BufBuilder attempted to grow() to 67108866 bytes, past the 64MB limit." error when trying to move a pipeline to be the only argument of a $FACET operator. The whole pipeline works fine without the $FACET, there is a lot of data to return, but the $OUT operator is used. However, once within the $FACET, the above is triggered, despite $OUT still being specified outside the $FACET. $OUT cannot be used within the $FACET arguments, thus I either don't seem to have the necessary control over the problem, or the $OUT operator's settings are ignored within the embedded pipeline, and the intermediate results, which are returned from the constituent pipelines, are undergoing a "to document" conversion, as is the case with other mentions of this error message.
|
| Comments |
| Comment by Ramon Fernandez Marina [ 18/Jun/18 ] |
|
brezniczky@gmail.com, unfortunately the $facet stage doesn't support result sets larger than 16MB at the moment – please watch and vote for SERVER-24804, which is open to lift this limitation. Thanks, |