Cluster Administration
This document describes administrative operations on a running Alluxio cluster on Kubernetes, such as upgrading to a new version and adding new workers.
Upgrading to a newer Alluxio version
Upgrade the Operator
Upload the new docker images corresponding to the new Alluxio operator version to your image registry and unpack the helm chart of the operator. Refer to the installation doc for details.
Run the following command to apply the new changes to the cluster.
Upgrade the Alluxio cluster
Before the operation you should know:
When the upgrade operation starts, the coordinator, workers, and the DaemonSet FUSE will perform rolling upgrade to use the new image. The existing CSI FUSE pods will not be restarted and upgraded, and only the new pods will use the new image.
While the cluster is being upgraded, the cache hit rate may decrease slightly, but will fully recover once the cluster is fully running again.
Following the steps to upgrade the cluster:
Upload the new docker images corresponding to the new Alluxio version to your image registry. Refer to the installation doc for details.
Update the
imageTag
fields inalluxio-cluster.yaml
to reflect the new Alluxio version. In the following example the newimageTag
will beAI-3.3-7.0.0
.Run the following command to apply the new changes to the cluster.
Scaling the size of the cluster
Scale Up the Workers
Before the operation you should know:
While the cluster is being upgraded, the cache hit rate may decrease slightly, but will fully recover once the cluster is fully running again.
Following the steps to scale up the workers:
Change the
alluxio-cluster.yaml
to increase thecount
in theworker
. In the following example we will scale from 2 workers to 3 workers.Run the following command to apply the new changes to the cluster.
Last updated