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

Use only IANA registered network ports for Couchbase Services

    XMLWordPrintable

Details

    Description

       

      Although our best practice advises end users to not run other software on the same machine as their Couchbase instances, there's a number of reasonable valid use cases such as monitoring agents and backup utilities which are colliding with our port numbers.

      Search for a Couchbase default network port such as 8091 on IANA - http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=8091  and you'll see we're using network ports registered to other services.  

       

      Service Name  Port Number Transport Protocol  Description Assignee  Contact  Registration Date 
      jamlink 8091 tcp Jam Link Framework [Evgeniy_Filatov [Evgeniy_Filatov 2009-11-25

       

      Port Number Registered Colliding Couchbase Description 
      8091 Yes Yes Used by the Couchbase Web Console for REST/HTTP traffic.
      8092 No No  Used to access views, run queries, XDCR and update design documents.
      8093 No No  Used by query services for REST/HTTP traffic.
      8094 No No  External HTTP port for the Search service
      9100 Yes Yes Internal index admin port (-adminPort).
      9101 Yes Yes  Internal index scan port (-scanPort).
      9102 Yes Yes  Internal index HTTP port (-httpPort).
      9103 Yes Yes  Internal index build port (-streamInitPort).
      9104 Yes Yes  Internal index build port (-streamCatchupPort ).
      9105 Yes Yes  Internal index maintenance port (-streamMaintPort).
      9998 Yes Yes  Internal REST port.
      9999 Yes Yes  Internal GSI port used by the internal administrators.
      11207 No No  Used by smart client libraries to access data nodes using SSL. This is a memcached SSL port.
      11209 No No  Internal Bucket Port.
      11210 No No  Used by smart client libraries or Moxi to directly connect to the data nodes. The XDCR client uses this port as well as the SDKs. This is a memcached port.
      11211 Yes No  Used by pre-existing Couchbase Server and memcached (non-smart) client libraries (such as Moxi).
      11214 No No Used for SSL XDCR data encryption.
      11215 No No  Used for SSL XDCR data encryption.
      18091 No No Used by the Couchbase Web Console for REST/HTTP traffic with SSL.
      18092 No No  Used to access views, run queries, XDCR and update design documents with SSL.
      18093 No No  N1QL SSL port
      4369 Yes No Erlang Port Mapper ( epmd )
      21100 to 21299 (inclusive) No No Node data exchange.
      6060 No No Used internally on the local host. Not used for communication between cluster nodes
      11213 No No Used internally on the local host. Not used for communication between cluster nodes

       
      Anything which is not registered and not colliding we should register with IANA,  anything that is already colliding we should look to move the port to an unused space and register it for our use.
       
      I will make sub-tasks for this for each Couchbase component which is affected.

      Attachments

        Issue Links

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

          Activity

            People

              malarky Chris Malarky
              ianmccloy Ian McCloy (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty