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

Metadata crash consistency

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: WT2.6.1
    • Component/s: None
    • None

      If there is a crash during a WT_SESSION::create, WT_SESSION::drop or WT_SESSION::rename operation, WiredTiger can end up with metadata entries that have no corresponding file.

      This may not be fully fixable for rename without making these operations transactional, but for create and drop, we should be able to order operations (including filesystem, log and metadata flushes) so that metadata is left consistent regardless of crashes during the operation.

            Assignee:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Reporter:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: