Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4844

Only log an informational message when a set read-timestamp is older than the oldest timestamp.

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.1, 4.3.1, 4.2.0-rc2, 4.0.14
    • Component/s: None
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      Storage Engines 2019-06-17
    • Backport Requested:
      v4.2, v4.0

      Description

      In this example, an error message is being logged when the read timestamp is behind the oldest timestamp, which ends up going through the WT error handler.

      This affects MongoDB because we log that at the highest level, "E", and is reported as a fatal error even though it is a routinely handled error.

      One suggestion would be to have these errors logged as messages instead of errors. They are helpful for debugging purposes, but do not need to be reported as errors.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              keith.bostic Keith Bostic
              Reporter:
              louis.williams Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: