Should not crash server when socket is closed in log server manager

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Server Integration
    • Fully Compatible
    • ALL
    • SESIPowerPlay - 2026-03-10, SESI DracoPotato - 2026-03-24
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When we encounter error code UNAVAILABLE, "Socket closed" we current fatal crash. This is the the correct behaviour, instead we should attempt to reestablish a connection to the log server standby and retry our request.

            Assignee:
            Adeline Chen
            Reporter:
            Adeline Chen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: