[SERVER-65906] Unable to see stack trace when BufBuilder attempts to grow past 64MB limit Created: 22/Apr/22 Updated: 25/Sep/23 Resolved: 25/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Shin Yee Tan | Assignee: | [DO NOT USE] Backlog - Storage Execution NAMER |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution NAMER
|
| Sprint: | Execution Team 2022-05-16, Execution Team 2022-05-30, Execution Team 2022-06-13, Execution Team 2022-06-27, Execution Team 2022-07-11, Execution Team 2022-08-08, Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-10-17, Execution Team 2022-11-14, Execution Team 2022-12-12, Execution Team 2022-11-28, Execution Team 2022-12-26 |
| Participants: |
| Description |
|
Add a printStackTrace when uasserting this error to be able to better diagnose what caused it. |
| Comments |
| Comment by Connie Chen [ 25/Sep/23 ] |
|
Closing as we're unsure if this would help diagnostics, if anyone does have a use case where this would be helpful please re-open for triage |
| Comment by Gregory Noma [ 13/Jun/22 ] |
|
I'm not sure if a tripwire assertion will work here (at least as things currently stand), since we actually expect this error code in some of our tests. We wouldn't want to turn those expected cases into test failures. Another workaround here could be to print a stack trace if the testing proctor is enabled. It may also be worthwhile to see whether there's a semantic difference between this error code (13548) and BSONObjectTooLarge. We could also improve the error message, since "BufBuilder attempted to grow() to " << minSize << " bytes, past the 64MB limit" isn't particularly helpful, especially from an external point of view. |
| Comment by Connie Chen [ 26/Apr/22 ] |
|
tripwire assertion makes sense, but we want to avoid adding a failpoint |