升级 RDI
了解如何升级现有 RDI 安装
升级 VM 安装
按照以下步骤升级 RDI 的现有 VM 安装：
-
从Redis下载中心下载RDI安装程序（在模块、工具和集成类别中）并将其解压到您的。 首选安装文件夹。
-
转到安装文件夹：
cd rdi_install/$RDI_VERSION -
Run the
upgradescript as a privileged user. Note that you must pass your RDI password to the script unless the password is empty.sudo ./upgrade.sh --rdi-password <redis-rdi-password>
Recovering from failure during a VM upgrade
If the previous version is v1.4.4 or later, go to the rdi_install/<PREVIOUS_VERSION>
directory and run sudo ./upgrade.sh, as described in the section
Upgrading a VM installation above.
If the version you are replacing is earlier than v1.4.4, follow these steps:
-
Run redis-di --version to check the current version.
If the version is the new one, copy the previous version
of the RDI CLI to /usr/local/bin with the following command:
sudo cp rdi_install/<PREVIOUS_VERSION>/deps/rdi-cli/<OS>/redis-di usr/local/bin
-
Check that the CLI version is correct by running redis-di --version.
Then, go to the rdi_install/<PREVIOUS_VERSION> directory and run the
following command;
sudo redis-di upgrade --rdi-host <RDI_REDIS_HOST> --rdi-port <RDI_REDIS_PORT>
Note:
If the collector-source or the processor are not in the Running state during
the upgrade, you must run redis-di deploy and check again that they are both in the
Running state.
Upgrading a VM installation with High availability
If there is an active pipeline, the upgrade process will involve upgrading RDI on the active
VM first which will cause downtime for the collector-source (see
Upgrade a VM installation above). Afterwards, the passive
VM will be upgraded. Switching over won't eliminate the downtime because switching between
VMs also requires a about a minute of downtime.
Upgrading a Kubernetes installation
Follow the steps below to upgrade an existing
Kubernetes
installation of RDI:
-
Download the new versions of the images, if you are using a private registry:
docker pull redis/rdi-processor:tagname
docker pull redis/rdi-operator:tagname
docker pull redis/rdi-api:tagname
docker pull redis/rdi-monitor:tagname
docker pull redis/rdi-collector-initializer
docker pull redis/rdi-collector-api
-
Download the RDI helm chart tar file from the
Redis download center.
-
Run the helm upgrade command:
helm upgrade [RELEASE_NAME] [CHART]
Note that you don't need to
deploy
again after this step.
Verifying the upgrade
Check the upgrade with the following command:
sudo k3s kubectl get all -n <namespace>
You should find that all the pods are running (they will have 1/1 in the READY column of the
command's output).
Check for any pods that don't have 1/1 in the READY column (which is the second
column). For example, the pod below has 0/1 in the second column, which indicates the
deployment hasn't worked:
<pod_name> 0/1 CrashLoopBackOff 1881 (91s ago) 6d17h
You can also check that the latest version is running using the following command on one of
the pods:
sudo k3s kubectl describe <pod_name> -n <namespace>
Search for the image tag Image: docker.io/redis/<pod_name>:<version/image_tag>
in the command's output to verify the version.
If you find that the upgrade hasn't worked for any reason, then run the helm upgrade
command again (as described in the section
Upgrading a Kubernetes installation above),
but this time with the previous version you were upgrading from. This will restore your
previous working state.
What happens during the upgrade?
The upgrade process replaces the current RDI components with the new versions:
-
Firstly, the control plane components are replaced. At this point, the pipeline
is still active but monitoring will be disconnected.
-
Secondly, the pipeline data path components are replaced with the new versions.
If a pipeline is active while upgrading, the collector-source will be restarted
as a result of restarting the collector-initializer. The pipeline will pause for
about two minutes but it will catch up very quickly after restarting.
The pipeline data and state are both stored in Redis, so data will never normally
be lost during the downtime while upgrading.
On this page