Ranger service management via ADCM
The ADCM UI provides actions to manage the Ranger service and its components. For information on how to run service actions, refer to ADPS service actions.
The actions available for the Ranger service are listed in the table below.
| Action | Description |
|---|---|
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. When selected, 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 |
Restart |
Restarts the service. When you run this action, the option Apply configs from ADCM is available. When selected, all service configurations defined in ADCM settings will be applied during the service restart. Otherwise, the service restarts without applying configurations from ADCM |
Remove |
Removes the service from the cluster.
This action should be used to remove already installed services.
Whereas the |
Add additional Ranger Admin |
Adds an additional Ranger Admin to one or more hosts. Running this action opens the host-component mapping interface where you can add new Ranger Admin components |
Move Ranger Admin User synchronizer |
Moves Ranger Admin User synchronizer to another host. Running this action opens a window in which you need to specify a new host for this component |
Set password |
Allows you to set a password for a user. Running this action opens a window in which you need to specify a username and a password that will be set for that user |
Migrate DB schema |
Allows you to migrate from an internal database to an external one (MySQL/PostgreSQL) |
Ranger has just one component, which has actions of its own — Ranger KMS.
| Action | Description |
|---|---|
Add |
Adds a Ranger KMS instance to a host |
Shrink |
Removes a Ranger KMS instance from a host |