[SERVER-25981] race in log component settings Created: 06/Sep/16 Updated: 19/Nov/16 Resolved: 26/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.15 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Cotter | Assignee: | Matt Cotter |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Platforms 2016-09-19, Platforms 2016-10-10 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The reported bug is that right now, calling setMinimumLoggedSeverity during shouldLog can trigger the dassert in shouldLog. However, the assert isn't that useful because we need that path to be fast, and what we really should synchronize is the writes in setMinimumLoggedSeverity (which is called much less frequently). |
| Comments |
| Comment by Githook User [ 26/Sep/16 ] |
|
Author: {u'username': u'Machyne', u'name': u'Matt Cotter', u'email': u'matt.cotter@mongodb.com'}Message: |