[SERVER-32192] unclear error message when agg exceeds 64MBs document size Created: 06/Dec/17  Updated: 01/Dec/23

Status: Backlog
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Asya Kamsky Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Query Execution
Participants:
Case:

 Description   

On some complex aggregations users get back:

exception: BufBuilder attempted to grow() to 67108876 bytes, past the 64MB limit.
Mongo Server error (MongoCommandException): Command failed with error 13548: 'BufBuilder attempted to grow() to 67108876 bytes, past the 64MB limit.' on server localhost:27017.
{
    "ok" : 0.0,
    "errmsg" : "BufBuilder attempted to grow() to 67108876 bytes, past the 64MB limit.",
    "code" : NumberInt(13548),
    "codeName" : "Location13548"
}

This is very opaque. It would be nice to provide a nicer error message that at least gives them an idea of where to start looking.



 Comments   
Comment by Charlie Swanson [ 03/Apr/18 ]

After some attempts to come up with a solution here, this turned out to be pretty difficult to reproduce, and the fix isn't exactly obvious. Moreover, re-compiling the code takes forever on a laptop after changing such a core library as BufBuilder, so I'm putting this back on the backlog and will look for a different ticket for the student.

Comment by David Storch [ 14/Mar/18 ]

Assigning this to charlie.swanson since a CUNY student he's working with is working on a pull request for this.

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