To replace a host that uses KUMA storage with another one:
./kdt invoke kuma --action removeHosts --param hostInventory=<path_to_inventory_file>
./kdt invoke kuma --action addHosts --param hostInventory=<path_to_inventory_file>
The host with the KUMA storage is replaced with another one.
If your storage configuration includes a shard containing two replicas, and you replaced the second replica host with a new one by using the steps described above, then you may receive an error when installing a new replica. In this case, the new replica will not work.
To fix an error when adding a new replica of a shard:
/opt/kaspersky/kuma/clickhouse/bin/client.sh
If this host is unavailable, run the client on any other host with a replica included in the same storage cluster.
SYSTEM DROP REPLICA '<replica number of read-only node>' FROM TABLE kuma.events_local_v2
SYSTEM DROP REPLICA '<replica number of read-only node>' FROM ZKPATH '/clickhouse/tables/kuma/<shard number of read-only node>/kuma/events_local_v2
SYSTEM RESTORE REPLICA kuma.events_local_v2
Operability of the added host with a replica is restored.
Page top