DataStax OpsCenter Documentation

OpsCenter reference

This section contains miscellaneous information about OpsCenter.

OpsCenter and OpsCenter agent ports

The following table lists the default port numbers used by OpsCenter and the OpsCenter Agents:

Port Description
OpsCenter ports
8888 OpsCenter website. The opscenterd daemon listens on this port for HTTP requests coming directly from the browser. Configurable in opscenterd.conf.
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. (DataStax Enterprise only)
61620 OpsCenter monitoring port. The opscenterd daemon listens on this port for TCP traffic coming from the agent.
OpsCenter agents ports (on the monitored nodes)
7199 JMX monitoring port. Each agent opens a JMX connection to its local node (the Cassandra or DataStax Enterprise process listening on this port). The JMX protocol requires that the client then reconnect on a randomly chosen port (1024+) after the initial handshake.
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 DataStax Enterprise cluster.
9290 Hadoop Job Tracker Thrift port. The Job Tracker listens on this port for Thrift requests coming from the opscenterd daemon. (DataStax Enterprise only)
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. (DataStax Enterprise only)
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. (DataStax Enterprise only)
61621 OpsCenter agent port. The agents listen on this port for SSL traffic initiated by OpsCenter.
22 SSH port. Configurable in opscenterd.conf.
Solr Port and Demo applications port
8983 Solr Port and Demo applications port.
Cassandra client port
9160 Each agent makes Thrift requests to its 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.

Debian and Ubuntu Package install locations

These packages are installed into the following directories:

  • /var/lib/opscenter (SSL certificates for encrypted agent/dashboard communications)
  • /var/log/opscenter (log directory)
  • /var/run/opscenter (runtime files)
  • /usr/share/opscenter (JAR, agent, web application, and binary files)
  • /etc/opscenter (configuration files)
  • /etc/init.d (service startup script)

CentOS, OEL, and RHEL Package install locations

These packages are installed into the following directories:

  • /var/lib/opscenter (SSL certificates for encrypted agent/dashboard communications)
  • /var/log/opscenter (log directory)
  • /var/run/opscenter (runtime files)
  • /usr/share/opscenter (JAR, agent, web application, and binary files)
  • /etc/opscenter (configuration files)
  • /etc/init.d (service startup script)

Binary Tarball distribution install locations

The tar installation creates the following directories in the <install_location> directory:

  • /agent (agent installation files)
  • /bin (startup and configuration binaries)
  • /conf (configuration files)
  • /content (web application files)
  • /doc (license files)
  • /lib and /src (library files)
  • /log (OpsCenter log files)
  • /ssl (SSL files for OpsCenter to agent communications)