If you have a firewall running on the nodes in your Cassandra or DataStax Enterprise cluster, you must open up the following ports to allow communication between the nodes, including certain Cassandra ports. If this isn't done, when you start Cassandra (or Hadoop in DataStax Enterprise) on a node, the node will act as a standalone database server rather than joining the database cluster.
| Port | Description |
|---|---|
| Public Facing Ports | |
| 22 | SSH (default) |
| DataStax Enterprise Specific | |
| 8012 | Hadoop Job Tracker client port. The Job Tracker listens on this port for job submissions and communications from task trackers; allows traffic from each Analytics node in a cluster. |
| 8983 | Solr port and Demo applications website port (Portfolio, Search, Search log) |
| 50030 | Hadoop Job Tracker website port. The Job Tracker listens on this port for HTTP requests. If initiated from the OpsCenter UI, these requests are proxied through the opscenterd daemon; otherwise, they come directly from the browser. |
| 50060 | Hadoop Task Tracker website port. Each Task Tracker listens on this port for HTTP requests coming directly from the browser and not proxied by the opscenterd daemon. |
| OpsCenter Specific | |
| 8888 | OpsCenter website. The opscenterd daemon listens on this port for HTTP requests coming directly from the browser. |
| Inter-node Ports | |
| Cassandra Specific | |
| 1024+ | JMX reconnection/loopback ports. See description for port 7199. |
| 7000 | Cassandra inter-node cluster communication. |
| 7199 | Cassandra JMX monitoring port. After the initial handshake, the JMX protocol requires that the client reconnects on a randomly chosen port (1024+). |
| 9160 | Cassandra client port (Thrift). OpsCenter agents makes Thrift requests to their local node on this port. Additionally, the port can be used by the opscenterd daemon to make Thrift requests to each node in the cluster. |
| DataStax Enterprise Specific | |
| 9290 | Hadoop Job Tracker Thrift port. The Job Tracker listens on this port for Thrift requests coming from the opscenterd daemon. |
| OpsCenter Specific | |
| 50031 | OpsCenter HTTP proxy for Job Tracker. The opscenterd daemon listens on this port for incoming HTTP requests from the browser when viewing the Hadoop Job Tracker page directly. |
| 61620 | OpsCenter monitoring port. The opscenterd daemon listens on this port for TCP traffic coming from the agent. |
| 61621 | OpsCenter agent port. The agents listen on this port for SSL traffic initiated by OpsCenter. |