[SERVER-19054] Don't be too chatty about periodic tasks taking a few ms Created: 19/Jun/15 Updated: 19/Sep/15 Resolved: 19/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.5, 3.1.5 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Backport Completed: | |
| Sprint: | Quint Iteration 5 |
| Participants: |
| Description |
|
Right now any background task that takes 3 ms or longer will result in a log message. The lock manager cleanup may take a few ms to clean all 128 or so buckets (though it will release/reacquire mutexes between buckets), causing one log message per minute on a normally operating system. So, we should only log operations taking more than 100ms or so. |
| Comments |
| Comment by Githook User [ 19/Jun/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: (cherry picked from commit d09fdf2b5887bfd6773f1a6da374a1ff7fc0e242) |
| Comment by Geert Bosch [ 19/Jun/15 ] |
|
Not fixing this will cause spam to the log once we backport |
| Comment by Githook User [ 19/Jun/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |