HBase service management via ADCM

Eugenia Kuzina

The ADCM UI provides actions to manage the HBase service and its components. For information on how to run service actions, refer to ADH service actions.

The actions available for the HBase service are listed in the table below.

Action Description

Add/Remove components

Running this action opens the component-host mapping interface where you can add, remove, and distribute HBase components. When running this action, you can specify the following parameters on the Configuration step:

  • Remove RegionServer without region unloading. When set to true, removes the RegionServer component without unloading data from it.

  • Limit the number of threads used by the region mover. Sets the maximum number of threads for the RegionMover process.

  • Timeout for moving regions. If regions cannot be moved within the specified timeout, the process exits with error.

Check

Runs service-specific tests to check the health of the service and its components

Start

Starts the service. When you run this action, the option Apply configs from ADCM is available. If it is set to true, all service configurations defined in ADCM settings will be applied on the service startup. Otherwise, the service starts without applying configurations from ADCM

Stop

Stops the service

Remove

Removes the service from the cluster. This action should be used to remove already installed services. Whereas the delete control can be used to remove a non-mapped service (a service which components have not been distributed among cluster hosts)

Restart

Restarts the service. When you run this action, the option Apply configs from ADCM is available. If it is set to true, all service configurations defined in ADCM settings will be applied during the service restart. Otherwise, the service restarts without applying configurations from ADCM ​.

The service supports the Rolling restart option that allows you to restart its components one by one (or in batches) rather than all at once. This feature helps to minimize the service downtime during restarts.

The Rolling restart option has the following parameters:

  • Limit the number of threads used by the region mover — the maximum number of regions that can be moved in parallel.

  • Timeout for moving regions — maximum time allowed to move regions before the operation fails. If regions cannot be moved within the allocated timeout, the restart process exits with an error.

  • Graceful restart RegionServers — enables/disables a graceful restart of RegionServer components. This parameter can cause regions to be moved multiple times, which can degrade the HBase client performance.

  • Roll masters — allows restarting HBase Master Server components one by one. If set to false, all HBase Master Server components are restarted in parallel.

  • max_wait_time — the maximum timeout in seconds to wait for checking the results after the restart (Znode checks).

  • pause_after_masters_restart — the idle timeout in seconds after restarting HBase Master Servers. May be required for initialization/stabilization needs.

Manage Ranger plugin

Enables or disables Ranger plugin for HBase. During this action RegionServers are restarted. When a RegionServer is shutdown, regions hosted by that RegionServer are moved to other RegionServers before stopping the current RegionServer. When you run this action, you have to specify the following parameters: Limit the number of threads used by the region mover for graceful RegionServer restarting and Timeout for moving regions for graceful RegionServer restarting. If regions are not moved by the timeout value, the action is interrupted, and an error occurs

Reconfig and graceful restart

Applies settings specified in ADCM UI and restarts the HBase service. During this action RegionServers are restarted. When a RegionServer is shutdown, regions hosted by that RegionServer are moved to other RegionServers before stopping the current RegionServer. When you run this action, you have to specify the following parameters: Limit the number of threads used by the region mover for graceful RegionServer restarting and Timeout for moving regions for graceful RegionServer restarting. If regions are not moved by the timeout value, the action is interrupted, and an error occurs
HBase components actions
Action Description

Check

Verifies whether all the component instances in the cluster work correctly

Restart

Restarts all the component instances in the cluster

Start

Starts all the component instances in the cluster

Stop

Stops all the component instances in the cluster
Found a mistake? Seleсt text and press Ctrl+Enter to report it