Skip to content

JPS

Jump to bottom
Zhamri Che Ani edited this page Nov 28, 2023 · 1 revision

When you start an Apache HBase cluster, several Java processes are initiated to run the various components of HBase. Using the jps command, you can list these processes. Here are the key Java processes typically seen for a fully operational HBase environment:

  1. HMaster: This is the master server for HBase. It coordinates the HBase cluster and is responsible for administrative operations such as creating and deleting tables, balancing regions, etc.

  2. HRegionServer: These are the worker nodes in HBase. Each RegionServer hosts a set of regions, manages reads and writes on those regions, and performs region splitting and merging.

  3. HQuorumPeer (if using embedded ZooKeeper): HBase can use an embedded ZooKeeper instance for managing cluster coordination and metadata. Each server running a ZooKeeper instance will have this process. If you're using an external ZooKeeper cluster, you won't see this process as part of the HBase setup.

  4. HBase Thrift Server (optional): If you're using the Thrift gateway to connect to HBase using other programming languages, this server process might be running.

  5. HBase REST Server (optional): If you're using the REST interface to interact with HBase, this server process might be running.

Note that this list assumes a relatively standard setup. Depending on your specific configuration, additional services or fewer services might be running. For example, in a development environment, you might have everything running on a single machine, whereas in a production environment, these components would be distributed across multiple machines. Also, if you're using additional tools or custom services with HBase, there might be other processes as well.

Clone this wiki locally