Ozone service management via ADCM

Contents

Overview

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

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

Ozone service actions
Action Description

Add/Remove components

Running this action opens the component-host mapping interface where you can add, remove, and distribute Ozone components

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

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

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)

Manage Ranger plugin

Enables or disables Ranger plugin for Ozone

The Ozone has five components:

  • Ozone Datanode

  • Ozone Manager

  • Ozone Recon

  • Ozone S3G

  • Ozone Storage Container Manager

All of these components have the same set of available actions listed in the table below.

Ozone components actions
Action Description

Add/Remove

Allows you to remove or add the component to the cluster hosts. When you run this action, a window with components and hosts is displayed, and you can redistribute the component among the hosts as described in the Add components article

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