UNIX socket file should reflect actual port, not port parameter

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • Networking & Obs 2024-12-09
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When passing in ServerGlobalParams.port = 0, the UNIX socket file that gets created uses suffix -0 instead of the port that's actually allocated. This artificially creates file conflicts when trying to avoid port collisions. Ideally, this file would be suffixed with the actual port, rather than -0 in such a case.

            Assignee:
            Amirsaman Memaripour
            Reporter:
            William Qian (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: