Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-31651

Improve experience dealing with port conflicts

    XMLWordPrintable

Details

    • Port conflicts
    • To Do

    Description

      An umbrella ticket to cover the work needed across the platform when encountering any port conflict.

      Should include the necessary work in the individual processes, logging, UI (i.e. to indicate a service is down), etc.

      The way it should work for services in general is as follows:

      • If the server is configured as IPv4, then:
        • The service must be able to bind against its ports under IPv4
        • The service does not have to be able to bind against these ports under IPv6. It should try to bind, but OK if it fails (i.e. if IPv6 is not available or the ports are being used by another process). It’s OK if the service does not try to optionally bind under IPv6 – especially for internal ports. For external ports the service should try to optionally bind.
      • If the server is configured as IPv6 then the previous statements apply with IPv4 and IPv6 reversed.

      Don’t think about it in terms of required, optional, off. Rather think about it in terms of whether the server is configured for IPv4 or IPv6.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              sharal.sonia Sharal Sonia (Inactive)
              perry Perry Krug
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty