[SERVER-21959] Do not truncate stack traces in log messages Created: 18/Dec/15 Updated: 25/Jan/17 Resolved: 30/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.3, 3.3.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Backport Completed: | |
| Sprint: | Sharding E (01/08/16) |
| Participants: |
| Description |
|
The JSON object in stack trace lines can exceed the standard log line length limit. We should not truncate them, anyways, as they are useful for debugging and are not derived from user input, so are unlikely to grow without bound. |
| Comments |
| Comment by Githook User [ 29/Jan/16 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: (cherry picked from commit 79901a7837f58f2c12d505995a316614e871faef) |
| Comment by Githook User [ 29/Jan/16 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: (cherry picked from commit 7e7ea93facc494fbc393f7170d50b371fbf5f9f0) |
| Comment by Githook User [ 30/Dec/15 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: |
| Comment by Githook User [ 21/Dec/15 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: |