[SERVER-21036] don't spin in oplog deleter thread Created: 20/Oct/15 Updated: 27/Oct/15 Resolved: 21/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | 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 |
| Operating System: | ALL |
| Sprint: | QuInt B (11/02/15) |
| Participants: |
| Description |
|
The WiredTigerRecordStoreThread used to have a sleep in it to handle cases where things weren't ready to delete (e.g. storage engine not yet initialized), but the sleep was removed as part of the oplogStones project. We need to add the sleep back in for these exceptional cases, to avoid spinning hard on server startup (and spamming the system log at debug log level 1). |
| Comments |
| Comment by Githook User [ 21/Oct/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |