Cluster Monitoring

http://${VEARCH_URL} is the vearch service.

Cluster Status

  1. curl -XGET http://${VEARCH_URL}/cluster/stats

Health Status

  1. curl -XGET http://${VEARCH_URL}/cluster/health

Server Status

  1. curl -XGET http://${VEARCH_URL}/servers

Partition Status

  1. curl -XGET http://${VEARCH_URL}/partitions

Clean lock

  1. curl -XGET http://${VEARCH_URL}/clean_lock

The cluster will be locked when creating a table. If the service is abnormal during this process, the lock will not be released and will need to be manually cleared before a new table can be created.

Replica expansion and contraction

  1. curl -XPOST -H "content-type: application/json"  -d'
  2. {
  3.     "partition_ids":[1],
  4.     "node_id": 1,
  5.     "method": 0
  6. }
  7. ' http://${VEARCH_URL}/partition/change_member

method=0: Add a copy of shard id 1 on node id 1; method=1: Delete the copy of shard id 1 on node id 1.

Cluster data migration

You can copy the data of a certain cluster to a new cluster through the following methods to realize cluster data migration.

  1. Create a new target cluster

The number of nodes in the new cluster should be consistent with that of the cluster to be migrated, a complete Vearch system should be deployed, and the processes of all ps nodes in the new cluster should be killed.

  1. Metadata synchronization

Use the mirror function of etcd to copy the metadata of the cluster to be migrated to the target cluster. etcdctl is the client tool for etcd.

The operation command is as follows:

  1. export ETCDCTL_API=3
  2. # The principle of etcd mirroring is to read the key row by row and write it to another cluster. Among them: sourceMasterIP is a node of the original cluster master, and targetMasterIP is a node of the target cluster master.
  3. # ETCDCTL_API=3 ./etcdctl make-mirror target --endpoints=source
  4. ETCDCTL_API=3 ./etcdctl make-mirror ${targetMasterIP}:2370 --endpoints=${sourceMasterIP}:2370

3. Delete the /$cluster_name/server meta-information of the target cluster cluster_name can be found in the configuration file config.toml

  1. export ETCDCTL_API=3
  2. ./etcdctl --endpoints=http://${targetMasterIP}:2370 del /$cluster_name/server --prefix

4. Copy vector data

  1. scp -r root@sourcePsIP:/export/vdb/baud root@targetPsIP:/export/vdb
  2. ...

sourcePsIP is the IP of the PS node of the cluster to be migrated, and targetPsIP is the IP of the PS node of the target cluster. Here you only need to ensure that the ps node IPs of the cluster to be migrated and the target cluster are migrated one-to-one, and no special order is required.