New API for Hardware Corruption Logs leveraging WiredTiger Unique IDs

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Logging
    • None
    • Storage Engines - Transactions
    • SE Transactions - 2026-01-02, SE Transactions - 2026-02-13
    • 5

      This ticket outlines the development of a new API or use the existing API for logging hardware corruption events. The API will utilise the unique ID feature within WiredTiger to ensure each corruption event is uniquely identifiable and can be accurately tracked.

      Acceptance Criteria:

      • A new API must be created to support the logging of hardware corruption events.
      • The API must leverage the existing WiredTiger unique ID feature for each log entry.
      • Each log entry must contain a unique ID and relevant corruption details.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Ravi Giri
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: