Enterprise Analytics Processes
- concept
Enterprise Analytics creates a number of different processes on each node. Enterprise Analytics creates processes from a set of binaries that get installed by the product installer.
The tables on this page list out all of the Enterprise Analytics processes. It’s important that you allow each of these processes to run and access files on the nodes. Otherwise, Enterprise Analytics does not function properly. Depending on your security environment, you may need to explicitly approve these processes and their binary directories in your security policy.
Linux
The following table lists the Enterprise Analytics processes that run on Linux platforms.
Process | Description | Path |
---|---|---|
|
Process that acts as a bridge between |
|
|
Service that’s used to encrypt the cluster configuration stored on disk |
|
|
Data service providing cluster topology updates to legacy SDKs |
|
|
Utility in Go to get disk usage stats |
|
|
Erlang port process (wrapper) used to talk to the |
|
|
Couchbase Cluster Manager run as Erlang virtual machines - |
|
|
Erlang-specific process which acts as a name server for Erlang distribution |
|
|
Erlang-specific process used to collect CPU: 1 for |
|
|
Erlang-specific process used to collect memory usage: 1 for |
|
|
Built-in Erlang port process that’s used to perform name service lookup |
|
|
Open source tool sigar that’s used to collect system information |
|
|
Erlang-specific process that’s used to supervise the available disk space: 1 for |
|
|
Wrapper for |
|
|
Utility used to collect Enterprise Analytics logs. Is seen only during log collection. |
|
|
JVM running the Enterprise Analytics Service |
|
|
Go-wrapper that communicates with |
|