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

Don't truncate files when running "wt" on a database with logging

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT2.0
    • Labels:

      Description

      While trying to manually get statistics after a LinkBench run with logging enabled, Alex and I managed to truncate data files, then truncate the log so that data was lost. I don't have a record of the exact steps, but it involved killing MySQL without closing the connection, then running "wt stat", so we didn't expect the results we saw.

      The main problems are:

      • commands like "wt stat" and "wt printlog" shouldn't write files at all; and
      • the "log=(enabled)" configuration is off by default, and when it is enabled, it automatically implies both running recovery and truncating logs afterwards. This makes "wt printlog" potentially remove the log files we want to examine after a crash.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sue.loverso Sue LoVerso
                Reporter:
                michael.cahill Michael Cahill
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: