[SERVER-21729] Log where oplog stones were placed at log-level 0 when sampling Created: 02/Dec/15 Updated: 03/Dec/15 Resolved: 02/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc6 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QuInt D (12/14/15) |
| Participants: |
| Description |
|
Knowing where the initial markers were placed has aided in investigating peculiar oplog truncation-related behavior multiple times during the 3.2 RC period. Proposal is to
|
| Comments |
| Comment by Githook User [ 02/Dec/15 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: Log additional messages that include the size and number of records in |