Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-21729

Log where oplog stones were placed at log-level 0 when sampling

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0-rc6
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      QuInt D (12/14/15)

      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

      1. change this message to be logged at log-level 0 so the information is more generally available.
      2. log the earliest and latest optimes when sampling the oplog at startup to better understand how good of a sample was taken.

        Attachments

          Activity

            People

            Assignee:
            max.hirschhorn Max Hirschhorn
            Reporter:
            max.hirschhorn Max Hirschhorn
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: