Details
-
Technical task
-
Resolution: Unresolved
-
Major
-
None
-
4.6.0
-
None
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.
https://www.iana.org/form/ports-services
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. See parent JIRA MB-22254
Ports for ns_server:
| 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. |
| 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. |
I think these are also ns_server ports ?
| 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 |