Ozone replication manager overview
Learn about Ozone's Replication Manager (RM), how it performs the throttling of tasks, and the configurations you can use to control the throttling tasks.
The RM is a service which runs inside the leader Storage Container Manager (SCM) daemon in a cluster. Its role is to make both RATIS and Erasure Coded data durable. It does this by periodically checking the health of all the containers in the cluster, and taking actions for any containers which are not healthy. Those actions can be creating new replicas of RATIS containers, reconstructing Erasure Coded data, closing replicas, removing any unnecessary replicas, and so on.
The RM process is split into stages. First, it checks containers and identifies those with problems. Second, it takes actions on the problematic containers.
The thread that checks each container in the first stage runs periodically. You can
configure its interval by using the
configuration. Default is 5 minutes.
The threads that take action on problematic containers in the second stage also run
periodically with a default of 30 seconds. You can configure them by using the