Update on CentOS 7

Attention! This guide is applicable only for CentOS 7. If you are using CentOS 8 or VEOS, ignore this guide.

Due to certain limitations in ClickHouse, changes were made to the dependencies of our fastor package. These changes ensure the correct functioning of the package on CentOS 8 and VEOS, but may cause issues on CentOS 7 due to the inability to handle the specified dependencies.

Step-by-Step Guide

Step 1. If you are receiving large amounts of data, it is recommended to:

Stop the receivers:

fastor-stop

Wait for the inserts to complete in the database:

clickhouse-client --query="select * from system.processes sp where sp.query like 'insert into%'" | wc -l

Stop the database:

fastor-db-stop

Step 2. Clear the yum cache:

yum clean all

Step 3. Run the installation script to update the repositories:

source <(curl https://vasexperts.ru/install/fastor-rpm_install.sh)
The script will not be completed successfully. The script output will contain errors indicating that ClickHouse dependencies cannot be resolved.

Step 4. Check the output of the command:

rpm -qa | grep clickhouse

If the output shows different states for all packages:

clickhouse-client-23.4.2.11-1.x86_64
clickhouse-server-23.4.2.11-1.x86_64
clickhouse-common-static-23.4.2.11-1.x86_64

then you need to remove these packages:

rpm -e fastor clickhouse-client-23.4.2.11-1.x86_64 clickhouse-server-23.4.2.11-1.x86_64 clickhouse-common-static-23.4.2.11-1.x86_64

Step 5. Update ClickHouse:

yum install clickhouse-common-static-24.2.2.71 clickhouse-server-24.2.2.71 clickhouse-client-24.2.2.71
The package versions should be exactly as specified in the command

Step 6. If the file /usr/lib/systemd/system/clickhouse-server.service contains the parameter TimeoutStartSec=0, it needs to be removed. This affects the startup of ClickHouse on CentOS 7.

Then run the command:

systemctl daemon-reload

Step 7. Install the latest version of fastor:

yum install fastor

Step 8. Restart ClickHouse in repair mode:

fastor-db-restart-repair

Step 9. Update the database schema:

fastor-db-scheme

Step 10. Restore the .env file:

mv "/var/qoestor/backend/.env.rpmsave" "/var/qoestor/backend/.env"

Step 11. Restart the receivers:

fastor-restart