[SERVER-16057] mongo::profile() shouldn't reuse BufBuilder when profile collection created Created: 10/Nov/14 Updated: 11/Jul/16 Resolved: 14/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | J Rassi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
When profiling is enabled but the system.profile collection does not exist, the operation is serialized into a BufBuilder, then the collection is created, and then the operation is re-serialized into the remaining space of the same BufBuilder. The second serialization needs to use a new BufBuilder (otherwise, any operation that serializes to >32MB will trip an invariant when the BufBuilder is attempted to be resized past its 64MB maximum). Affects master as of 1537472f. |
| Comments |
| Comment by Githook User [ 14/Nov/14 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |