Investigate diagnostic gaps for crash loops

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Persistence
    • SE Persistence backlog
    • None

      We recently had a case where a cluster entered a crash loop due to what appears to be hardware-related corruption. The issue was resolved after performing an initial sync, but we’d like to understand how we can capture enough information in the future to properly investigate similar incidents.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Jasmine Bi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: