[SERVER-14467] Capture S2 debug log messages Created: 05/Jul/14 Updated: 31/Jul/15 Resolved: 08/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo, Logging |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 1 |
| Labels: | community-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Sprint: | Server 2.7.4, Server 2.7.5 | ||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Description |
|
Debug log messages in the third party S2 Geometry Library (typically triggered by bad user input) are now visible in the server logs by setting the verbosity of the S2 log component to 5. 2 ways to enable S2 debug log messages:
Sample logs in 2.7.5 at log level 5 generated from running jstests/core/geo_invalid_polygon.js:
--------- It is non-trivial to debug issues with Geo queries that fail due to invalid polygons. There are a number of very good error messages that occur within S2 that make these problems significantly easier to debug. Can we find a way to capture these S2 logs and have them pushed over to our logfiles? Example log line: https://github.com/mongodb/mongo/blob/master/src/third_party/s2/s2loop.cc#L110 |
| Comments |
| Comment by Githook User [ 08/Aug/14 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |